checked Sep 23, 2026 3:40 PM UTC · Supabase's official status page
Supabase is slower than normal.
2 of 11 components affected
Statusfield watches Supabase alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
29 reports published by Supabase in the last 30 days · 3 still open
When Supabase breaks, it is typically resolved in 2h 18m — median across 14 resolved incidents over 90 days.
monitoringSep 23 · 10:20 UTC
A fix has been implemented for the affected tenants and we are monitoring the results. We will continue to monitor the situation and will provide further updates as more information becomes available.
Reported by Supabase on their status page.
resolvedSep 23 · 10:49 UTC
This incident has been resolved.
Reported by Supabase on their status page.
resolvedSep 22 · 12:20 UTC
This incident has been resolved. Following the restart of the affected Supavisor node, error rates returned to normal and no further disruptions have been observed during the monitoring period. All services are operating normally.
Reported by Supabase on their status page.
resolvedSep 22 · 09:05 UTC
The latency has recovered and the incident is now resolved.
Reported by Supabase on their status page.
resolvedSep 19 · 22:12 UTC
Project lifecycle operations are behaving normally.
Reported by Supabase on their status page.
resolvedSep 16 · 20:36 UTC
This incident has been resolved.
Reported by Supabase on their status page.
resolvedSep 16 · 12:27 UTC
This incident has been resolved.
Reported by Supabase on their status page.
resolvedSep 16 · 09:33 UTC
This incident has been resolved.
Reported by Supabase on their status page.
resolvedSep 11 · 17:00 UTC
We observed latency issues over the weekend resulting in 504 errors primarily impacting customers on the Free tier. The incident has been resolved.
Reported by Supabase on their status page.
ResolvedSep 11 · 17:00 UTC
We observed latency issues over the weekend resulting in 504 errors primarily impacting customers on the Free tier. The incident has been resolved.
Reported by Supabase on their status page.
resolvedSep 11 · 19:06 UTC
This incident has been resolved.
Reported by Supabase on their status page.
ResolvedSep 11 · 19:06 UTC
This incident has been resolved.
Reported by Supabase on their status page.
resolvedSep 9 · 08:47 UTC
Between 05:50–06:05 UTC some customer using Supavisor in us-east-1 may have experienced brief dropped connections or connection disruptions. This issue was caused by an unexpected restart of Supavisor instances in the affected cluster. We apologize for any disruption caused.
Reported by Supabase on their status page.
ResolvedSep 9 · 08:47 UTC
Between 05:50–06:05 UTC some customer using Supavisor in us-east-1 may have experienced brief dropped connections or connection disruptions. This issue was caused by an unexpected restart of Supavisor instances in the affected cluster.We apologize for any disruption caused.
Reported by Supabase on their status page.
resolvedSep 4 · 08:18 UTC
Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.
Reported by Supabase on their status page.
ResolvedSep 4 · 08:18 UTC
Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.
Reported by Supabase on their status page.
resolvedSep 1 · 10:34 UTC
This incident has been resolved. Users should now be able to log in to the Supabase Dashboard normally. Projects and non-Dashboard traffic were unaffected throughout the incident.
Reported by Supabase on their status page.
ResolvedSep 1 · 10:34 UTC
This incident has been resolved. Users should now be able to log in to the Supabase Dashboard normally.Projects and non-Dashboard traffic were unaffected throughout the incident.
Reported by Supabase on their status page.
resolvedAug 31 · 19:06 UTC
Project creation has returned to baseline consistently.
Reported by Supabase on their status page.
ResolvedAug 31 · 19:06 UTC
Project creation has returned to baseline consistently.
Reported by Supabase on their status page.
resolvedAug 28 · 16:18 UTC
PostgreSQL 15 projects were failing to load /usr/lib/postgresql/15/lib/supautils.so because GLIBC_2.33 is unavailable on affected hosts. This disrupted database access in multiple regions. Rollback is now complete and we are seeing access restored to projects in the affected regions.
Reported by Supabase on their status page.
resolvedAug 31 · 15:57 UTC
Response times have recovered in all regions. This issue is now resolved.
Reported by Supabase on their status page.
ResolvedAug 31 · 15:57 UTC
Response times have recovered in all regions. This issue is now resolved.
Reported by Supabase on their status page.
resolvedAug 27 · 18:24 UTC
The fix has remained stable across all regions, and the issue has been resolved.
Reported by Supabase on their status page.
resolvedAug 24 · 16:38 UTC
This incident has been resolved.
Reported by Supabase on their status page.
resolvedSep 15 · 12:48 UTC
We have made a repeat reminder for resolution to the appropriate parties in Myanmar. As no further response has been received, this incident will be resolved. We recommend customers still experiencing issues to contact their ISP for assistance or review our workarounds proposed here: https://supabase.com/blog/navigating-regional-network-blocks
Reported by Supabase on their status page.
ResolvedSep 15 · 12:48 UTC
We have made a repeat reminder for resolution to the appropriate parties in Myanmar. As no further response has been received, this incident will be resolved. We recommend customers still experiencing issues to contact their ISP for assistance or review our workarounds proposed here: https://supabase.com/blog/navigating-regional-network-blocks
Reported by Supabase on their status page.
identifiedSep 23 · 07:26 UTC
We have rolled out the deployment process changes to eu-central-2 and continue to monitor. We will provide additional updates as we make this change to other regions. Once this change is implemented across all regions, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue.
Reported by Supabase on their status page.
UpdateSep 11 · 23:41 UTC
We continue to monitor progress and are slowly updating each region. Thank you for your patience on this issue.
Reported by Supabase on their status page.
