Last checked
Open source Firebase alternative for building production-grade applications with Postgres database.
Experiencing an issue?

Supabase è down?
Degraded performance
The current official status of Supabase cannot be verified. The latest stored provider observation indicated degraded performance. 0 reports were recorded for Supabase in the last 24 hours. Last official check: .
Source: official status pageShare your experience to help others stay informed.
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Loading reports… · Last 24 hours
Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
| Start | End | Reports | Status |
|---|
Official status checked
Supabase is experiencing issues
Official provider statusOfficial incident active
Delays in project provisioning — We're investigating delays affecting project pause/restore, branch creation, and project provisioning across multiple regions. Some users may see failures or slowness when performing these operations. We'll share updates as we learn more.
Official provider statusOfficial incident active
401 errors due to JWT rejections — As part of the incident remediation flow, we have separately identified "/lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found" error between 11:15 - 16:24 UTC today affecting PostgREST. This has been fixed and we can see the error rates have subsided.
Official provider statusOfficial incident active
Network access issues affecting a limited number of users in Myanmar — We have reached out to the ISPs that have been involved in the connectivity challenges for users in Myanmar. We are continuing to work to address the issue.
Official provider status0 outage reports in the last 24 hours.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 425h 8mOngoing | Yes | Unknown | ||
| 467h 37mOngoing | Yes | Minor | ||
| 467h 42mOngoing | Yes | Unknown | ||
| 3h 9m | Yes | Minor | ||
| 9m | Yes | Minor | ||
| 1h 14m | Yes | Critical | ||
| 601h 11mOngoing | Yes | Minor | ||
| 3h 53m | Yes | Unknown |
Planned work published by the official provider.
The maintenance has been completed successfully.
Started 14 lug 2026, 03:00 UTC · Resolved 14 lug 2026, 05:14 UTC
The scheduled maintenance has been completed.
Started 26 giu 2026, 03:00 UTC · Resolved 26 giu 2026, 04:00 UTC
The scheduled maintenance has been completed.
Started 9 giu 2026, 13:00 UTC · Resolved 9 giu 2026, 15:00 UTC
Condividi i tuoi pensieri su Supabase
Sii il primo a commentare!
Uptimus monitora Supabase tramite la fonte ufficiale e normalizza incidenti, manutenzioni e componenti in uno stato coerente.
Questa pagina include attualmente 28 componenti monitorati, 75 incidenti, 47 manutenzioni e 35 giorni di storico noto.
Uptimus è un servizio indipendente e non è affiliato a Supabase. Uno stato regolare non garantisce che ogni utente, dispositivo o area sia esente da problemi.
Ricevi un avviso quando Supabase o un componente monitorato segnala un'interruzione grave o critica. Gli avvisi possono essere inviati tramite i canali attivi nel workspace, inclusi email, push e integrazioni configurate. La cronologia disponibile contiene 75 incidenti indicizzati e offre un contesto oltre lo stato attuale. Un incidente recente indicizzato è stato «Delays in project provisioning».
Ricevi avvisi su prestazioni degradate, impatto parziale e incidenti che non rappresentano un'interruzione completa. Uptimus monitora attualmente 28 componenti di Supabase: Analytics, ap-northeast-1, API Gateway, ap-northeast-2. Gli avvisi possono essere inviati tramite i canali attivi nel workspace, inclusi email, push e integrazioni configurate.
Le pagine pubbliche di Downdetector sono basate soprattutto sulle segnalazioni degli utenti. Uptimus le combina con incidenti ufficiali, manutenzioni e stato dei componenti quando il provider li pubblica.
| Criteri di confronto | Uptimus | Downdetector |
|---|---|---|
| Segnalazioni della community su Supabase |
The scheduled maintenance has been completed.
Started 3 giu 2026, 13:00 UTC · Resolved 3 giu 2026, 15:00 UTC
The scheduled maintenance has been completed.
Started 2 giu 2026, 15:00 UTC · Resolved 2 giu 2026, 18:00 UTC
The scheduled maintenance has been completed.
Started 1 giu 2026, 13:00 UTC · Resolved 1 giu 2026, 15:00 UTC
The scheduled maintenance has been completed.
Started 26 mag 2026, 13:00 UTC · Resolved 26 mag 2026, 15:00 UTC
The scheduled maintenance has been completed.
Started 14 mag 2026, 18:00 UTC · Resolved 14 mag 2026, 20:00 UTC
| Incluso |
| Incluso |
| Baseline adattiva che distingue casi isolati da un’interruzione estesa | Incluso | Incluso |
|---|
| Attività delle ultime 24 ore e visualizzazione regionale | Incluso | Incluso |
|---|
| Un solo spazio per siti, provider di stato, giochi Steam e app e giochi Android | Incluso | Prodotto separato |
|---|
| Avvisi e-mail, push e webhook dallo stesso spazio | Incluso | Prodotto separato |
|---|
| Aggiornamenti ufficiali e cronologia dello stato di Supabase | Incluso | Basato sulle segnalazioni |
|---|
| Stato dei componenti e manutenzioni mostrati separatamente | Incluso | Limitato nelle pagine pubbliche |
|---|
Rate this service
No reviews yet