Resolvido · durou 1 h
Falha do Supabase em 22 de outubro
Os relatos do Supabase subiram para 31 por hora e ficaram altos por 1 h.
- Início
- 11:00
- 22 de outubro de 2026 · UTC
- De volta ao normal
- 12:00
- 1 h depois
- Pico
- 31/h
- 31× o normal
- Incidente de Supabase
- 2 h 13 min
- Elevated Mgmt API Error Rates in Multiple Regions
Relatos durante a falha
O que Supabase disse
status.supabase.comElevated Mgmt API Error Rates in Multiple Regions
- Resolvido · 13:42
Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.
- Monitoramento · 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 publicou a primeira atualização 29 min depois que os relatos começaram a subir.
O Supabase está fora do ar agora?
Status ao vivo, relatos de hoje e outras falhas anteriores.