Incidentsby GlyphDegraded Supavisor performance in sa-east-1 region.
Oct 26, 18:51 UTCOct 26, 20:02 UTC
Duration
1h 11m
Impact
Informational
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Not listed by the vendor.
Final update
This incident has been resolved. The impact began at 2:00 UTC causing a small fraction of queries in the affected region to be slower. At 11:00 UTC, the issue escalated and became more apparent as p95 latency increased. By 15:00 UTC, the degradation became widespread, with median query performance showing high variance and p95 consistently elevated. Higher than usual connection times could also be perceived during the incident.
Timeline
- Resolved · Oct 26, 20:02 UTC
This incident has been resolved. The impact began at 2:00 UTC causing a small fraction of queries in the affected region to be slower. At 11:00 UTC, the issue escalated and became more apparent as p95 latency increased. By 15:00 UTC, the degradation became widespread, with median query performance showing high variance and p95 consistently elevated. Higher than usual connection times could also be perceived during the incident.
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