Supabase Outage History

We have identified that the issue is with an upstream DNS provider, causing DNS creation delays for newly created, unpaused, or updated databases. Our team is actively monitoring the situation and will provide further updates as more information becomes available.

We have identified the cause of the issue and are working to restore normal log ingestion. Customers may continue to experience delays in new logs appearing.

We have identified the cause of the SSO login failures affecting the us-east-1 region and are working to implement a fix. We will continue to provide updates as progress is made.

We noticed the search function for our documentation was not available as it should be. We're making the necessary updates to fix that problem.

We have identified the cause of delays in DNS records creation and are actively working on a fix. We will continue to provide updates as things progress.

We have identified and mitigated the issue that was blocking DNS updates. DNS record creation is succeeding, and latency has returned to normal levels. A subset of projects that encountered provisioning failures during the incident will require DNS records to be backfilled, and we are actively remediating these affected projects.

We have identified the cause of the resize issues and are evaluating options for mitigating the problem.

We have implemented a fix to the authentication issue and are monitoring for recovery.

We have identified the issue and are working to re-enable the ingestion of logs.

We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results.

We have identified an issue where S3 endpoints for keys with special characters will be broken. We are actively investigating the correct mitigation for this issue.

A likely mitigation has been identified and we are discussing the proper implementation method.

We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress

Our infrastructure provider experienced a connectivity issue in the EU-CENTRAL-1 (Frankfurt) Region, between 4:11 PM PDT and 6:24 PM PDT, which has now been resolved. As a result of this incident, a number of Supabase projects were left in a stuck state. Our team is actively working through the list of impacted projects to restore normal functionality as quickly as possible. We will continue to provide updates as restoration work progresses.

We are continuing to work on a fix for this issue.

The majority of impacted projects have now been recovered, and functionality has been restored for most customers. Our team continues to work through the remaining affected projects individually to restore normal functionality as quickly as possible. We will continue to provide updates as this work progresses.

The majority of impacted projects have now been recovered, and functionality has been restored for most customers. Our team continues to work through the remaining affected projects individually to restore normal functionality as quickly as possible. We will continue to provide updates as this work progresses.

We have identified the issue and are actively working on a fix. We will share another update as soon as we have more information.

We've identified the issue and are implementing a fix. If you need access to logs from the affected period (starting at approximately 22:15 UTC), please contact Support and we will work with you to retrieve them.

We have identified likely reasons for the problem and are investigating options for resolution. We advise all customers to ensure they are using valid JWT keys with their projects.

We have identified the cause of the creation delays and are actively working to address the problem.

We continue our investigation into how to mitigate the project creation delays. We are examining relevant data paths in detail.

We have identified options for mitigation and are discussing the best implementation methods for them.

Project creation is recovering. We are actively tracking recovery.

We have identified the cause of the 500 errors and are implementing a fix.

We have identified the root cause and are working on a fix.

We are continuing to work on a fix for the issue and will provide another update as soon as we have more information to share.

We are redirecting project creation to more healthy regions and working to continue to increase the success rate in ca-central-1. A longer startup time is expected while project creation is recovering in ca-central-1.

We are investigating an issue affecting the Performance Advisors feature for some projects. Affected users may be unable to run Performance Advisors and may see an error when attempting to view advisor results in the Dashboard. Our team has identified the cause and is working to implement a fix. We will provide another update as soon as more information becomes available.

We continue to work on a fix for advisor results in the Dashboard. Affected users may be unable to run Performance Advisors and may see an error when attempting to view advisor results in the Dashboard.

We are currently seeing delays affecting the setup of Realtime, Storage, and shared pooler services for newly created projects. Customers may experience longer than expected provisioning times after creating a new project, and some project lifecycle operations may also be delayed while setup completes. Our team is has identified the issue and are working to restore normal provisioning times. We will provide another update as soon as we have more information.

We have identified an issue with the Restore to New Project beta feature and we are implementing a fix. The Restore to New Project beta feature will be temporarily unavailable while we fix this issue. We will update this page when the fix has been rolled out.

The team has identified the root cause of the issue and is currently rolling out a fix across the platform. We will continue to monitor the rollout and provide another update once it has been completed.