Supabase reported this major-impact incident on its official status page on Oct 22, 2026, 11:29 UTC. It was resolved after 2h 13m.
Right now Supabase is operational. Live Supabase status →
Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.
A mitigation has been applied. Error rates and latency have returned to normal levels. We’re continuing to monitor to ensure sustained stability before resolving this incident.
We are investigating elevated error rates and increased response times on the Management API across multiple regions. Some operations that depend on it, such as creating new projects, may fail or be slow. This is also causing logins to supabase.com to timeout.
We are investigating elevated error rates and increased response times on the Management API across multiple regions. Some operations that depend on it, such as creating new projects, may fail or be slow.
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 65 incidents in the last 90 days, 24 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history