Supabase Incident History

Project upgrades have remained stable, we are resolving this incident.

We have deployed a tested fix for the upgrade issue impacting some projects. The fix has been effective and we are monitoring for continued stability.

We are continuing to test the fix to project upgrades. We will update again when the fix is applied.

The team has identified a likely fix and is consolidating the details in order to move to thorough testing. We will update again when the fix is applied.

We are continuing to fix project upgrade issues and are investigating further remediation. We will provide our next update within the next 14 hours.

We are developing a fix for the upgrade issues.

We have identified the cause of the upgrade delays and are working on a fix.

We are continuing to investigate project upgrade issues.

We are investigating a potential issue that could result in a delay or failure in some users' project upgrades.

After monitoring, we have confirmed that issues affecting Management API performance have been resolved.

We are continuing to monitor the the Management API to ensure no further intermittent occurrences appear. We will provide another update within 24 hours.

We have identified the root cause and deployed a fix. We will continue to monitor the behavior through the weekend to ensure no further occurrences appear.

We are continuing mitigation efforts for the intermittent issues with the Management API.

Cause isolation is continuing. We are doing work to ensure the accuracy of the understood cause in order to have confidence in the mitigation method under consideration.

We've isolated the cause of the network issues with the Management API and we are working on a fix.

We have been alerted that our Management API is experiencing performance degradation due to intermittent network issues. Users who experience the problem are encouraged to log out and log back in to the dashboard as that has cleared the issue in many cases. Additionally, users can retry failed actions as needed. We are actively investigating a persistent fix.

A preventative fix (Supabase CLI v2.111.0 ) has been released to ensure that new Function deployments are not affected. As the underlying issue has been addressed and new deployments should no longer be affected, we are resolving this incident. All impacted users are now able to re-deploy their Functions again. In exceptional cases, Support will continue working directly with customers who require additional remediation.

We are working on a permanent fix for issue affecting bulk Function deployments. In parallel, we are manually assisting customers who have reported the issue through support tickets.

Our fix has completed rollout and we are monitoring for full resolution.

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

We continue to investigate the root cause of this issue. Some deployment operations have recovered, but we are still investigating reports of failures affecting bulk deployments and updates to existing Edge Functions.

We are still identifying the root cause of the issue; however, if you are experiencing issues with your Edge Functions, redeployment should resolve that issue. We apologize for any inconvenience.

We are continuing to investigate this issue.

Per-function deployment appears to be working successfully. However, bulk function deployments with the `supabase functions deploy` command appear to still be experiencing issues. Additionally, we are aware of reports of issues updating existing function deployments. We are continuing to investigate these issues.

We have determined and rolled back the change that led to this issue. Users who were experiencing issues with deployments should now be able to deploy successfully.

Only a subset of users appear to be impacted by the issue with Edge Function deployments. We are investigating the root cause.

We are aware of some users experiencing issues with Edge Function deployments.

The incident has been resolved.

The upstream DNS provider has implemented a fix and is monitoring the results. We are seeing signs of recovery; we will continue to monitor the situation and will provide further updates as more information becomes available.

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're investigating issues updating DNS records for newly created, unpaused, or updated databases.

The intermittent networking issues have subsided. Management-api is operating normally now.

The intermittent networking issues have subsided. Management-api is operating normally now. We will continue to monitor for abnormal behavior.

We are continuing to investigate the issue. We will provide further updates as progress is made.

We have identified some anomalies that appear correlated to this issue and we are continuing to investigate.

We are continuing to investigate the issue.

We have been alerted that our management API is experiencing performance degradation due to intermittent network issues. Users who experience the problem are encouraged to log out and log back in to the dashboard as that has cleared the issue in many cases. We are actively investigating a persistent fix.

The issue has been resolved, and customers should now see new logs appearing as expected.

Log ingestion has been restored, and new logs are now appearing as expected. We will continue monitoring to ensure the issue is fully resolved.

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 are experiencing a problem with log ingestion. Customers may experience a lack of new logs being visible from their projects. We are investigating.

The issue has been resolved. SSO login functionality in the us-east-1 region has returned to normal, and all services are operating as expected.

We have rolled out a fix for the SSO login failures affecting the us-east-1 region. We are monitoring the results and will continue to observe the service to ensure stability before resolving the incident.

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 are investigating an issue causing SSO login failures in the us-east-1 region. Our team is actively investigating the cause and will provide updates as more information becomes available.

Documentation search functionality has been restored.

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.

This incident is resolved. DNS creation for new projects has been fixed since 20:35 UTC. Backfill of missing DNS records has been completed at 22:20 UTC. Please contact Support if your project seems impacted by missing DNS records.

All failed DNS creation has been backfilled, and customers should no longer see missing DNS records in their projects. DNS record creation and latency have returned to normal levels. We will continue to monitor before resolving this incident.

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 delays in DNS records creation and are actively working on a fix. We will continue to provide updates as things progress.

We are investigating failures in provisioning DNS records for projects, there may be delays in creation of DNS records for new or unpaused projects.

Project resizing has maintained expected performance in us-west-2.

We have a mitigation in place for resizing issues for projects in us-west-2. We will be monitoring going forward. If your project is in us-west-2, and you experience issues resizing going forward, please open a support ticket so we can directly assist you.

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

We are continuing to investigate this issue.

We have noticed an issue with project resizing in us-west-2 and are investigating.

Authentication operations have returned to normal consistently.

Authentication has returned to normal.

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

Some projects are experiencing authentication issues. We are actively investigating.