Resuelto · duró 1 h
Caída de Supabase el 22 de octubre
Los informes de Supabase subieron a 31 por hora y se mantuvieron altos durante 1 h.
- Inicio
- 11:00
- 22 de octubre de 2026 · UTC
- Vuelta a la normalidad
- 12:00
- 1 h después
- Pico
- 31/h
- 31× lo normal
- Incidente de Supabase
- 2 h 13 min
- Elevated Mgmt API Error Rates in Multiple Regions
Informes durante la caída
Lo que dijo Supabase
status.supabase.comElevated Mgmt API Error Rates in Multiple Regions
- Resuelto · 13:42
Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.
- Supervisando · 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.
- Investigando · 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.
- Investigando · 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 publicó su primera actualización 29 min después de que los informes empezaran a subir.
¿Está Supabase caído ahora mismo?
Estado en directo, informes de hoy y otras caídas anteriores.