Résolu · a duré 1 h

Panne de Supabase le 22 octobre

Les signalements pour Supabase ont grimpé à 31 par heure et sont restés élevés pendant 1 h.

Début
11:00
22 octobre 2026 · UTC
Retour à la normale
12:00
1 h plus tard
Pic
31/h
31× la normale
Incident de Supabase
2 h 13 min
Elevated Mgmt API Error Rates in Multiple Regions

Signalements pendant la panne

9:0013:50 UTC

Ce que Supabase a dit

status.supabase.com
Résolu11:29 – 13:42 · 2 h 13 min

Elevated Mgmt API Error Rates in Multiple Regions

  1. Résolu · 13:42

    Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.

  2. Surveillé · 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.

  3. En cours d'investigation · 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.

  4. En cours d'investigation · 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 a publié sa première mise à jour 29 min après le début de la hausse des signalements.

Supabase est-il en panne en ce moment ?

État en direct, signalements du jour et autres pannes passées.

État de Supabase maintenant →