Supabase Outage History

We are experiencing significant degraded performance across edge functions, mainly affecting deploy and retrieving function body. We have identified the root cause and are working on the fix now.

We're now seeing reduced error rates for Edge Functions. We've identified the root cause and are working on a fix.

Edge Functions deployments have returned to normal levels. We're now reviewing worker jobs that failed during the incident, including any backups that may have been affected. We'll re-queue these jobs once we've identified them, and we'll share more details on the status page. If you're noticing particular job failures that are unusual, please reach out to support.

We have identified the issue impacting log ingestion. Logs may be delayed or unavailable. We are working to restore normal functionality.

We are implementing a fix for the log ingestion issue, and traffic is beginning to recover. We are continuing to work toward full recovery.

We continue to work on a fix as traffic continues to recover. We will provide further updates as more information becomes available.

We are continuing to implement the fix as traffic recovers. We will provide further updates as progress continues.

We have identified the issue with the upgrade. To prevent issues, we have suspended the ability to upgrade projects while we resolve this issue. The problem is limited to upgrades from earlier versions of PG17 to the most recent release. We are working on a fix.

A fix has been developed and we are going through the review and implementation process.

The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.

We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.

Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon. This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available.

The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.

All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.

We have identified the issue causing some users to encounter permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard. We are working on a fix and will provide another update once it has been implemented.

We've identified the cause and are working on a fix.

We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

Projects running Postgres version 14 in us-east-1 and ap-northeast-2 may experience query slowness. We've identified the cause and are working on a fix.

We are continuing to work on a fix and will provide updates as things progress.

The fix has been implemented for ap-northeast-2 and we're working on implementing the fix for us-east-1. We will continue to provide updates as progress is made.

We have identified an issue related to the Auth service on some projects. We are actively working on a fix.

We have identified a subset of projects with a failing Auth service. Our team is working to remediate the issue.

We have identified why projects are becoming unresponsive and are implementing a mitigation.

A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.

Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.

We have rolled out a version of the fix across all regions that will prevent recurrence of the issue. Users still affected by project outages are encouraged to restart their projects.

We are seeing the mitigation steps having the desired effect. Project creation is recovering.