Supabase Outage History

Supabase is up right now

Pingoru has recorded 186 incidents for Supabase: 186 in the last 12 months and 83 in the last 90 days.

Source: status.supabase.com

186incidents recorded
186last 12 months
83last 90 days
26 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct16
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct47%
Pingoru began tracking Supabase in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20261351 of 720 (7%)
May 202613369 of 744 (50%)
June 202617243 of 720 (34%)
July 202625353 of 744 (47%)
August 202622547 of 744 (74%)
September 202636148 of 720 (21%)
October 202616275 of 589 (47%)

Incidents, newest first

Minor January 28, 2026 Errors when Updating auth configs with github branching 2h Database

Started Jan 28, 2026, 07:45 PM UTC· resolved Jan 28, 2026, 09:45 PM UTC

  1. investigating Jan 28, 2026, 07:45 PM UTC

    Some users are seeing errors when attempting to update auth configs on branches with github branching. This is only affecting branches, and is not affecting production projects. The team is currently investigating.

  2. identified Jan 28, 2026, 07:56 PM UTC

    We have identified the issue causing errors for these changes, and the team is working on a fix.

  3. monitoring Jan 28, 2026, 08:58 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jan 28, 2026, 09:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 28, 2026 Project Creation Issues - eu-west-1 4h 29m eu-west-1

Started Jan 28, 2026, 05:02 PM UTC· resolved Jan 28, 2026, 09:32 PM UTC

  1. investigating Jan 28, 2026, 05:02 PM UTC

    We are investigating issues affecting instance operations in the eu-west-1 region. This may impact new project creation, project unpauses, read replica creation, and upgrades. Existing projects remain unaffected.

  2. investigating Jan 28, 2026, 05:56 PM UTC

    Instance operations in eu-west-1 are impacted by an ongoing infrastructure provider incident causing network issues in the region. Affected operations include new project creation, unpauses, read replica creation, and upgrades. Existing projects are unaffected. Our provider is aware of the issue and we already see error rates and latency trending down. We will update as the situation progresses.

  3. identified Jan 28, 2026, 06:45 PM UTC

    We continue to monitor for resolution of the upstream provider incident.

  4. identified Jan 28, 2026, 07:55 PM UTC

    We are continuing to monitor for resolution of the upstream provider incident.

  5. identified Jan 28, 2026, 08:01 PM UTC

    We have received word from our upstream partner that their issue has been resolved. The team is currently testing all functionality on our side and cleaning up previously errored requests. Once we're confident things are back to normal, we'll resume project actions in the region.

  6. monitoring Jan 28, 2026, 08:13 PM UTC

    Project actions (creation, unpauses, read replica creation, upgrades) have been re-enabled, and the team is monitoring.

  7. resolved Jan 28, 2026, 09:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 28, 2026 Degraded Performance for Supavisor –

Started Jan 28, 2026, 06:00 AM UTC· resolved Jan 28, 2026, 06:00 AM UTC

  1. resolved Jan 28, 2026, 09:26 AM UTC

    Between 6am and 7am UTC our Supavisor cluster experienced instability, resulting in elevated error rates and increased client reconnects. The issue has since been resolved, and the service is operating normally. We are currently reviewing preventative measures to reduce the likelihood of recurrence.

Read the full incident report →

Minor January 14, 2026 Edge Function increased error rate in EU-West-1 1h 47m Edge Functions

Started Jan 14, 2026, 12:57 PM UTC· resolved Jan 14, 2026, 02:44 PM UTC

  1. investigating Jan 14, 2026, 12:57 PM UTC

    We are currently investigating this issue.

  2. identified Jan 14, 2026, 01:00 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jan 14, 2026, 01:12 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jan 14, 2026, 02:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 14, 2026 Elevated real-time error rates in ap-se-1 1h 6m Realtime

Started Jan 14, 2026, 09:01 AM UTC· resolved Jan 14, 2026, 10:07 AM UTC

  1. investigating Jan 14, 2026, 09:01 AM UTC

    We're currently investigating increased error rates across all regions

  2. monitoring Jan 14, 2026, 09:35 AM UTC

    The performance of the impacted components has improved.

  3. monitoring Jan 14, 2026, 09:59 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jan 14, 2026, 10:07 AM UTC

    We've confirmed that the elevated 5xx errors and high response times were isolated to the ap-southeast-1 region. Other regions remained healthy throughout the incident. Dashboards showed a sharp spike in 5xx errors and response times for ap-southeast-1, with metrics rapidly recovering after remediation steps. For more details, see the realtime-service combined dashboard. The incident was the result of a resource constraint. We have added the required resources and will take this into account in our future planning. We're continuing to monitor system health to confirm stability.

Read the full incident report →

Minor January 7, 2026 Some edge function deployment operations are timing out 1h 8m Edge Functions

Started Jan 07, 2026, 06:14 PM UTC· resolved Jan 07, 2026, 07:23 PM UTC

  1. investigating Jan 07, 2026, 06:14 PM UTC

    We are seeing increased timeouts when deploying edge functions and are currently investigating. Already deployed functions are not affected.

  2. identified Jan 07, 2026, 06:40 PM UTC

    For users experiencing this issue: esm.sh is having issues. Users can replace esm.sh with npm: or jsr imports to get function deploys to work.

  3. monitoring Jan 07, 2026, 06:54 PM UTC

    To address function deploy issues, replace esm.sh with npm: or jsr imports instead. This workaround is confirmed to work.

  4. resolved Jan 07, 2026, 07:23 PM UTC

    ESM has resolved their issue. All function deploy actions should now be working.

Read the full incident report →

Major December 24, 2025 Shared SMTP service has low deliverability for some users 8h 21m Auth

Started Dec 24, 2025, 03:33 PM UTC· resolved Dec 24, 2025, 11:55 PM UTC

  1. investigating Dec 24, 2025, 03:33 PM UTC

    We are currently investigating an issue where some users have reported failures when sending email via the Shared SMTP service. If you are impacted, and need email services working immediately, you can work around this immediately by following best practice for production use cases and configure custom SMTP: https://supabase.com/docs/guides/auth/auth-smtp

  2. investigating Dec 24, 2025, 03:58 PM UTC

    We are currently investigating an issue where some users have reported failures when sending email via the Shared SMTP service. This is also impacting newly creating projects. If you are impacted, and need email services working immediately, you can work around this immediately by following best practice for production use cases and configure custom SMTP: https://supabase.com/docs/guides/auth/auth-smtp

  3. investigating Dec 24, 2025, 05:01 PM UTC

    We are continuing to investigate this issue. An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp

  4. identified Dec 24, 2025, 05:41 PM UTC

    We have identified the issue, and we are working on the fix. An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp

  5. identified Dec 24, 2025, 06:30 PM UTC

    We have implemented a fix, and all new projects should now be fully operational. We are now working on backporting it to the affected projects. An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp

  6. identified Dec 24, 2025, 07:27 PM UTC

    We have implemented a fix, and all new projects should now be fully operational. We are rolling out a backporting fix to the affected projects; this is going to take around 3 hours. An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp

  7. identified Dec 24, 2025, 08:26 PM UTC

    A fix has been deployed, all new projects are now fully operational. We're currently backporting the fix to affected projects (30% complete). An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp

  8. identified Dec 24, 2025, 09:28 PM UTC

    We've deployed a fix and confirmed all new projects are fully operational. Remediation for previously affected projects is underway and 50% complete. An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp

  9. identified Dec 24, 2025, 10:31 PM UTC

    A fix has been deployed, all new projects are fully operational. We're currently backporting the fix to affected projects (69% complete). An immediate workaround is to use custom SMTP. More information available on configuring that here: https://supabase.com/docs/guides/auth/auth-smtp

  10. monitoring Dec 24, 2025, 11:42 PM UTC

    A fix has been deployed, all new projects are fully operational. We've finished backporting the fix to affected projects and now monitoring.

  11. resolved Dec 24, 2025, 11:55 PM UTC

    This incident has been resolved.

Read the full incident report →