Løst · varte 1 t
Driftsbrudd hos Supabase 22. oktober
Rapportene for Supabase steg til 31 i timen og holdt seg høye i 1 t.
- Startet
- 11:00
- 22. oktober 2026 · UTC
- Normalt igjen
- 12:00
- 1 t senere
- Topp
- 31/t
- 31× normalt
- Hendelse hos Supabase
- 2 t 13 min
- Elevated Mgmt API Error Rates in Multiple Regions
Rapporter under driftsbruddet
Hva Supabase sa
status.supabase.comElevated Mgmt API Error Rates in Multiple Regions
- Løst · 13:42
Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.
- Overvåker · 12:07
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.
- Undersøker · 11:32
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.
- Undersøker · 11:29
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.
Supabase publiserte sin første oppdatering 29 min etter at rapportene begynte å stige.
Er Supabase nede akkurat nå?
Live status, dagens rapporter og andre tidligere driftsbrudd.