Incidentsby GlyphError spikes in one of the ap-northeast-2 Supavisor clusters
Aug 24, 06:02 UTCAug 24, 09:51 UTC
Duration
3h 49m
Impact
Minor
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Not listed by the vendor.
Final update
The issue has been resolved.
Timeline
- Resolved · Aug 24, 09:51 UTC
The issue has been resolved.
- Monitoring · Aug 24, 09:13 UTC
We have applied a fix and are monitoring for full resolution. Errors have ceased in the last minutes and all connections are back to healthy.
- Investigating · Aug 24, 07:07 UTC
We are continuing to investigate the errors in ap-northeast-2 Supavisor clusters.
- Investigating · Aug 24, 06:02 UTC
We are investigating error spikes in the ap-northeast-2 Supavisor clusters. Users reported failures in connecting to postgres via Supavisor with the error: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode.
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