Supabase reported this minor-impact incident on its official status page on Sep 16, 2026, 17:53 UTC. It was resolved after 2h 42m.
Right now Supabase is degraded. Live Supabase status →
This incident has been resolved.
The fix has been rolled out to us-east-1. We will continue to monitor both regions for stability.
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.
We are continuing to work on a fix and will provide updates as things progress.
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.
Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Supabase reported 43 incidents in the last 90 days, 16 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history