Supabase reported this minor-impact incident on its official status page on Sep 16, 2026, 09:24 UTC. It was resolved after 3h 3m.
Right now Supabase is degraded. Live Supabase status →
This incident has been resolved.
Error rates have returned to normal, and the service is operating as expected. The team continues to investigate the underlying cause of the latency and spike in 503 errors.
We are investigating reports of increased Edge Function latency and elevated rates of HTTP 503 responses, beginning at approximately 06:00 UTC. Our team is working to identify the cause and will provide further updates as they become available.
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 47 incidents in the last 90 days, 17 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history