Supabase
SlowDegraded
Degraded since — Realtime latency
Recent incidents latest 10 by start time · newest first
Recovery estimateSimilar Supabase incidents typically clear in 1h 38m–20h 25m (median ~2h 46m).
Latest official update · We have taken preventative steps to expand our realtime cluster capacity and are continuing to monitor our system stability for full recovery.
Recovery estimateSimilar Supabase incidents typically clear in 1h 38m–20h 25m (median ~2h 46m).
Latest official update · Edge Functions deployments have returned to normal levels. We will continue monitoring for full recovery.
Resolved · lasted 5h 50m
Resolved · lasted 2h 56m
Resolved · lasted 1h 11m
Resolved · lasted 6d 19h 48m
Resolved · lasted 52m
Resolved · lasted 2h 3m
Resolved · lasted 1h 12m
Resolved · lasted 1h 46m
August 2026 worst confirmed state per UTC day · newest first
Clear all dayDegraded that dayDown that dayNo confirmed data
Questions from the forecast desk
Is Supabase down right now?
Supabase is degraded. Checked . Since . Incident: Realtime latency
Where does this data come from?
Tech Weather checks Supabase's official status page every five minutes.
How are unconfirmed signals handled?
Early signals need two independent sources and are always labeled unconfirmed. They never become a confirmed outage without the official status page.