Resuelto · duró 1 h
Caída de Supabase el 6 de octubre
Los informes de Supabase subieron a 75 por hora y se mantuvieron altos durante 1 h.
- Inicio
- 7:00
- 6 de octubre de 2026 · UTC
- Vuelta a la normalidad
- 8:00
- 1 h después
- Pico
- 75/h
- 75× lo normal
- Incidente de Supabase
- 1 h 10 min
- Increased errors on management api leading to project operation failures
Informes durante la caída
Lo que dijo Supabase
status.supabase.comIncreased errors on management api leading to project operation failures
- Resuelto · 9:03
This issue has been resolved and our error rates have returned back to normal. During this incident users would have observed unauthorized/5xx failures across multiple operations on the project operations and dashboard functions. We have since rolled out a fix and all functionality is restored.
- Supervisando · 8:13
We have identified a rollout causing error increase on management api dependant services, which is causing project operation failures and FGA Authentication errors across multiple functions. We have implementing a fix and observing recovery. Our teams are continuing to monitor for full resolution.
- Investigando · 7:55
We are continuing to investigate this issue.
- Investigando · 7:53
We are investigating an increase in errors on project update flows including creation, pausing/unpausing and upgrading across multiple regions.
Supabase publicó su primera actualización 54 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.