Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2
Sep 16, 17:53 UTCSep 16, 20:36 UTC
Duration
2h 42m
Impact
Minor
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Not listed by the vendor.
Final update
This incident has been resolved.
Timeline
- Resolved · Sep 16, 20:36 UTC
This incident has been resolved.
- Monitoring · Sep 16, 19:48 UTC
The fix has been rolled out to us-east-1. We will continue to monitor both regions for stability.
- Identified · Sep 16, 19:17 UTC
The fix has been implemented for ap-northeast-2 and we're working on implementing the fix for us-east-1. We will continue to provide updates as progress is made.
- Identified · Sep 16, 18:32 UTC
We are continuing to work on a fix and will provide updates as things progress.
- Identified · Sep 16, 17:53 UTC
Projects running Postgres version 14 in us-east-1 and ap-northeast-2 may experience query slowness. We've identified the cause and are working on a fix.
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