Upstream provider issue affecting repo sync in US-EAST-1 (N. Virginia)
Oct 20, 08:43 UTCOct 20, 12:21 UTC
Duration
3h 38m
Impact
Critical
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Not listed by the vendor.
Final update
We’re closing this incident in favour of the higher-impact event now tracked here: status.supabase.com/incidents/595nsxm9hj59. Please follow that incident for further updates.
Timeline
- Resolved · Oct 20, 12:21 UTC
We’re closing this incident in favour of the higher-impact event now tracked here: status.supabase.com/incidents/595nsxm9hj59. Please follow that incident for further updates.
More from Supabase
Full historyInterruption in connections to Supavisor in eu-west-2lasted 1h 42mIncreased Errors with Project Lifecycle Operations in US-West-2lasted 2h 28mIntermittent 502/503 errors for pg_net calls to Edge Functionslasted 42mStorage issues in us-east-1 and eu-central-1lasted 16h 18mIntermittent errors on Supavisor Shared Pooler in us-east-2lasted 29mManagement API Postgres config updates overwriting previous updateslasted 2h 8m