Supabase Outage History

Started Jul 30, 2026, 08:57 PM UTC· resolved Jul 30, 2026, 09:50 PM UTC

1. investigating Jul 30, 2026, 08:57 PM UTC

   We are experiencing a problem with log ingestion. Customers may experience a lack of new logs being visible from their projects. We are investigating.

2. identified Jul 30, 2026, 09:33 PM UTC

   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.

3. monitoring Jul 30, 2026, 09:39 PM UTC

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

4. resolved Jul 30, 2026, 09:50 PM UTC

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

Read the full incident report →

Started Jul 30, 2026, 05:37 PM UTC· resolved Jul 31, 2026, 01:20 PM UTC

1. investigating Jul 30, 2026, 05:37 PM UTC

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

2. investigating Jul 30, 2026, 06:16 PM UTC

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

3. investigating Jul 30, 2026, 06:28 PM UTC

   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.

4. investigating Jul 30, 2026, 07:46 PM UTC

   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.

5. investigating Jul 30, 2026, 09:02 PM UTC

   We are continuing to investigate this issue.

6. investigating Jul 30, 2026, 10:21 PM UTC

   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.

7. investigating Jul 30, 2026, 11:40 PM UTC

   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.

8. identified Jul 31, 2026, 12:26 AM UTC

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

9. monitoring Jul 31, 2026, 03:13 AM UTC

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

10. identified Jul 31, 2026, 09:36 AM UTC

    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.

11. resolved Jul 31, 2026, 01:20 PM UTC

    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. Support will continue working directly with customers whose existing deployments require remediation.

Read the full incident report →

Started Jul 28, 2026, 09:24 PM UTC· resolved Jul 28, 2026, 10:07 PM UTC

1. investigating Jul 28, 2026, 09:24 PM UTC

   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.

2. identified Jul 28, 2026, 09:33 PM UTC

   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.

3. monitoring Jul 28, 2026, 09:53 PM UTC

   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.

4. resolved Jul 28, 2026, 10:07 PM UTC

   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.

Read the full incident report →

Started Jul 28, 2026, 02:06 PM UTC· resolved Jul 28, 2026, 02:13 PM UTC

1. identified Jul 28, 2026, 02:06 PM UTC

   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.

2. resolved Jul 28, 2026, 02:13 PM UTC

   Documentation search functionality has been restored.

Read the full incident report →

Started Jul 27, 2026, 08:34 PM UTC· resolved Jul 27, 2026, 10:36 PM UTC

1. investigating Jul 27, 2026, 08:34 PM UTC

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

2. identified Jul 27, 2026, 08:39 PM UTC

   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.

3. identified Jul 27, 2026, 08:53 PM UTC

   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.

4. monitoring Jul 27, 2026, 10:23 PM UTC

   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.

5. resolved Jul 27, 2026, 10:36 PM UTC

   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.

Read the full incident report →

Started Jul 27, 2026, 05:42 PM UTC· resolved Jul 27, 2026, 08:47 PM UTC

1. investigating Jul 27, 2026, 05:42 PM UTC

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

2. investigating Jul 27, 2026, 05:53 PM UTC

   We are continuing to investigate this issue.

3. identified Jul 27, 2026, 06:11 PM UTC

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

4. monitoring Jul 27, 2026, 07:01 PM UTC

   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.

5. resolved Jul 27, 2026, 08:47 PM UTC

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

Read the full incident report →

Started Jul 25, 2026, 02:11 PM UTC· resolved Jul 25, 2026, 02:45 PM UTC

1. investigating Jul 25, 2026, 02:11 PM UTC

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

2. identified Jul 25, 2026, 02:21 PM UTC

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

3. monitoring Jul 25, 2026, 02:25 PM UTC

   Authentication has returned to normal.

4. resolved Jul 25, 2026, 02:45 PM UTC

   Authentication operations have returned to normal consistently.

Read the full incident report →

Started Jul 23, 2026, 11:30 AM UTC· resolved Jul 23, 2026, 11:30 AM UTC

1. resolved Jul 23, 2026, 12:55 PM UTC

   Between 11:34 and 11:43 UTC, some tenants in the us-east-2 (Ohio) region experienced degraded connectivity during a connection pooler maintenance upgrade. The affected cluster has since recovered, and connectivity is operating as expected.

Read the full incident report →

Started Jul 22, 2026, 04:29 PM UTC· resolved Jul 22, 2026, 08:10 PM UTC

1. investigating Jul 22, 2026, 04:29 PM UTC

   We are experiencing a problem with log ingestion. Customers may experience a lack of new logs being visible from their projects. We are investigating.

2. identified Jul 22, 2026, 04:56 PM UTC

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

3. monitoring Jul 22, 2026, 05:49 PM UTC

   We have implemented a fix, and log ingestion has returned to normal. We will continue to monitor this issue to ensure it stays stable.

4. monitoring Jul 22, 2026, 06:40 PM UTC

   We are continuing to monitor log ingestion to ensure it remains stable.

5. resolved Jul 22, 2026, 08:10 PM UTC

   This issue is now resolved. Log ingestion has returned to normal and customers can now view project logs.

Read the full incident report →

Started Jul 17, 2026, 05:49 PM UTC· resolved Jul 18, 2026, 01:41 AM UTC

1. investigating Jul 17, 2026, 05:49 PM UTC

   Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.

2. investigating Jul 17, 2026, 06:16 PM UTC

   Project actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance.

3. investigating Jul 17, 2026, 06:47 PM UTC

   We have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel.

4. investigating Jul 17, 2026, 07:20 PM UTC

   We are testing mitigation options to attempt to restore project action performance.

5. identified Jul 17, 2026, 07:45 PM UTC

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

6. monitoring Jul 17, 2026, 08:21 PM UTC

   The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality.

7. resolved Jul 18, 2026, 01:41 AM UTC

   Project actions have been sustained at normal performance. This incident is resolved.

Read the full incident report →

Started Jul 16, 2026, 05:55 PM UTC· resolved Jul 16, 2026, 06:49 PM UTC

1. identified Jul 16, 2026, 05:55 PM UTC

   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.

2. identified Jul 16, 2026, 06:23 PM UTC

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

3. identified Jul 16, 2026, 06:32 PM UTC

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

4. resolved Jul 16, 2026, 06:49 PM UTC

   This incident has been resolved. A recent API Gateway deployment altered how certain special characters in S3 object key paths were encoded before reaching storage, causing signature verification failures (403) for affected requests. The change has been reverted and issue is now fixed.

Read the full incident report →

Started Jul 16, 2026, 07:00 AM UTC· resolved Jul 16, 2026, 11:35 AM UTC

1. identified Jul 16, 2026, 07:00 AM UTC

   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.

2. identified Jul 16, 2026, 07:02 AM UTC

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

3. identified Jul 16, 2026, 07:42 AM UTC

   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.

4. identified Jul 16, 2026, 09:16 AM UTC

   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.

5. monitoring Jul 16, 2026, 10:14 AM UTC

   All impacted projects have now been successfully restarted, and functionality has been restored. We are moving this incident to Monitoring for an additional hour while we continue to ensure stability. If you believe your project in eu-central-1 (Frankfurt) is still impacted by this issue, please open a support ticket and we'll work with you directly to investigate.

6. resolved Jul 16, 2026, 11:35 AM UTC

   The mitigation work for this incident has been completed, and we have not observed any further impact following the restoration of affected projects. This incident is now resolved. If you continue to experience issues that you believe are related to this incident in eu-central-1 (Frankfurt), please open a support ticket and our team will investigate.

Read the full incident report →

Started Jul 15, 2026, 12:04 AM UTC· resolved Jul 15, 2026, 12:50 AM UTC

1. investigating Jul 15, 2026, 12:04 AM UTC

   We are currently investigating an issue affecting the ability to view and manage authentication providers in the Supabase dashboard.

2. identified Jul 15, 2026, 12:25 AM UTC

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

3. monitoring Jul 15, 2026, 12:34 AM UTC

   A fix has been deployed for the issue that affects configuring Authentication Providers. We are monitoring the results to confirm the issue has been fully resolved.

4. resolved Jul 15, 2026, 12:50 AM UTC

   This issue has been resolved.

Read the full incident report →

Started Jul 09, 2026, 11:34 PM UTC· resolved Jul 10, 2026, 03:48 AM UTC

1. investigating Jul 09, 2026, 11:34 PM UTC

   We are currently investigating an issue affecting log ingestion across all regions. During this time, some logs may be delayed or unavailable.

2. investigating Jul 10, 2026, 12:02 AM UTC

   We are continuing to investigate the issue affecting log ingestion across all regions. Logs may be delayed or unavailable. We will provide another update as soon as more information becomes available.

3. investigating Jul 10, 2026, 12:36 AM UTC

   We are continuing to investigate the issue affecting log ingestion across all regions. Logs may be delayed or unavailable. We will provide another update as soon as more information becomes available.

4. investigating Jul 10, 2026, 01:25 AM UTC

   We continue to investigate an issue affecting log visibility that began at approximately 22:15 UTC. During this time, logs may be delayed or unavailable. Our team continues to investigate the underlying cause and will provide another update as more information becomes available. If you need access to logs from the affected period, please contact Support and we will work with you to retrieve them.

5. identified Jul 10, 2026, 02:53 AM UTC

   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.

6. monitoring Jul 10, 2026, 03:03 AM UTC

   We have implemented a fix for the issue affecting log visibility that began at approximately 22:15 UTC. Log ingestion has returned to normal. We are monitoring the system to ensure the issue is fully resolved. If you continue to experience missing or delayed logs from the affected period, please contact Support for assistance.

7. resolved Jul 10, 2026, 03:48 AM UTC

   This issue has been resolved. Log ingestion and log visibility have returned to normal operation. If you experience missing or delayed logs from the affected time period, please contact Support and we'll be happy to assist.

Read the full incident report →

Started Jul 08, 2026, 06:37 PM UTC· resolved Jul 08, 2026, 07:57 PM UTC

1. investigating Jul 08, 2026, 06:37 PM UTC

   We are aware of reports of elevated legacy JWT authorization errors on edge functions in some regions

2. identified Jul 08, 2026, 07:16 PM UTC

   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.

3. monitoring Jul 08, 2026, 07:28 PM UTC

   A rollback mitigation implemented by our team has addressed the problem. Edge functions have returned to normal. We will continue to monitor performance.

4. resolved Jul 08, 2026, 07:57 PM UTC

   Edge function operations are normal.

Read the full incident report →

Started Jul 08, 2026, 04:52 PM UTC· resolved Jul 08, 2026, 07:30 PM UTC

1. investigating Jul 08, 2026, 04:52 PM UTC

   We are aware of project creation taking longer than normal in AP regions. A retry should enable completion of creation for those impacted.

2. identified Jul 08, 2026, 05:17 PM UTC

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

3. identified Jul 08, 2026, 05:44 PM UTC

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

4. identified Jul 08, 2026, 06:12 PM UTC

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

5. identified Jul 08, 2026, 06:42 PM UTC

   Project creation is recovering. We are actively tracking recovery.

6. monitoring Jul 08, 2026, 06:59 PM UTC

   Recovery has continued and project creation in the relevant region has returned to normal. We will continue to monitor this for another 30 minutes.

7. resolved Jul 08, 2026, 07:30 PM UTC

   Project creation has returned to normal. The issue is now resolved.

Read the full incident report →

Started Jul 06, 2026, 02:45 PM UTC· resolved Jul 06, 2026, 04:10 PM UTC

1. investigating Jul 06, 2026, 02:45 PM UTC

   Multiple endpoints are returning 500 Internal server errors across our platform. We are investigating what has caused these errors.

2. investigating Jul 06, 2026, 02:47 PM UTC

   The 500 errors are limited to us-east-1, we are actively exploring causes.

3. investigating Jul 06, 2026, 03:10 PM UTC

   The scope of the errors is across regions in the Americas. We are narrowing down the likely causal chains.

4. identified Jul 06, 2026, 03:15 PM UTC

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

5. monitoring Jul 06, 2026, 03:42 PM UTC

   The fix has been applied and there are improvements to the error rates. We are continued to work on ensuring the underlying issue does not recur.

6. resolved Jul 06, 2026, 04:10 PM UTC

   Operations have returned to normal. We are implementing improvements to prevent similar recurrences in the future.

Read the full incident report →

Started Jul 02, 2026, 10:59 PM UTC· resolved Jul 03, 2026, 04:51 AM UTC

1. investigating Jul 02, 2026, 10:59 PM UTC

   We are seeing degraded project creation success rates in the ca-central-1 region. We are currently investigating the issue, and will provide an update soon.

2. identified Jul 02, 2026, 11:35 PM UTC

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

3. identified Jul 03, 2026, 12:26 AM UTC

   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.

4. identified Jul 03, 2026, 02:13 AM UTC

   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.

5. monitoring Jul 03, 2026, 02:56 AM UTC

   We have restored project creation startup time in ca-central-1 and are monitoring the situation for full recovery.

6. resolved Jul 03, 2026, 04:51 AM UTC

   The project creation in ca-central-1 has been restored.

Read the full incident report →

Started Jul 02, 2026, 02:26 PM UTC· resolved Jul 02, 2026, 05:14 PM UTC

1. identified Jul 02, 2026, 02:26 PM UTC

   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.

2. identified Jul 02, 2026, 03:42 PM UTC

   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.

3. monitoring Jul 02, 2026, 04:53 PM UTC

   We've deployed the fix and are now monitoring the issue.

4. resolved Jul 02, 2026, 05:14 PM UTC

   This issue is resolved and advisor results are now available in the Dashboard.

Read the full incident report →

Started Jul 01, 2026, 05:39 PM UTC· resolved Jul 01, 2026, 06:56 PM UTC

1. identified Jul 01, 2026, 05:39 PM UTC

   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.

2. monitoring Jul 01, 2026, 06:40 PM UTC

   Provisioning times and project lifecycle operations have returned normal. We will continue to monitor.

3. resolved Jul 01, 2026, 06:56 PM UTC

   This issue is now resolved. Provisioning times and project lifecycle operations have returned to normal.

Read the full incident report →

Started Jul 01, 2026, 03:16 PM UTC· resolved Jul 01, 2026, 07:04 PM UTC

1. identified Jul 01, 2026, 03:16 PM UTC

   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.

2. resolved Jul 01, 2026, 07:04 PM UTC

   We've rolled out a fix for the R2NP issue, and users should be able to execute the flow again.

Read the full incident report →

Started Jul 01, 2026, 02:40 PM UTC· resolved Jul 01, 2026, 04:12 PM UTC

1. investigating Jul 01, 2026, 02:40 PM UTC

   We are currently investigating an issue affecting the Edge Function API requests. Our team is working on a fix, and we will provide another update as soon as more information becomes available.

2. identified Jul 01, 2026, 02:59 PM UTC

   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.

3. monitoring Jul 01, 2026, 03:30 PM UTC

   We have implemented a fix, and error rates have returned to expected levels. We are continuing to monitor the platform closely to ensure the issue is fully resolved.

4. resolved Jul 01, 2026, 04:12 PM UTC

   Edge Function API requests have returned to normal. This issue is now resolved.

Read the full incident report →

Started Jun 30, 2026, 04:56 PM UTC· resolved Jun 30, 2026, 06:01 PM UTC

1. investigating Jun 30, 2026, 04:56 PM UTC

   We have detected increased rates of connection issues in a us-east-1 Supavisor cluster starting at 14:10 UTC. Our team is currently investigating.

2. monitoring Jun 30, 2026, 05:06 PM UTC

   We believe the issue has resolved. We are monitoring for any recurrence.

3. resolved Jun 30, 2026, 06:01 PM UTC

   We have not observed any increased rates of connection problems on the us-east-1 Supavisor cluster during our monitoring period. We are confident that the incident is resolved.

Read the full incident report →

Started Jun 30, 2026, 03:08 AM UTC· resolved Jul 13, 2026, 04:00 PM UTC

1. investigating Jun 30, 2026, 02:38 AM UTC

   We are currently investigating an issue affecting project creation in multiple regions.

2. investigating Jun 30, 2026, 02:43 AM UTC

   Project creation is impacted across multiple regions, we are investigating the root cause.

3. investigating Jun 30, 2026, 03:08 AM UTC

   We have identified the issue and confirmed that impact extends beyond project creation. Project creation, project resizing, branch provisioning, and project restarts are currently affected across multiple regions. We will share another update as soon as we have more information.

4. identified Jun 30, 2026, 03:38 AM UTC

   We have identified the issue and are working on a fix. Impact is currently affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will provide another update as soon as we have more information.

5. identified Jun 30, 2026, 04:32 AM UTC

   We are continuing to work on a fix for the issue and will provide updates as more information is available.

6. identified Jun 30, 2026, 05:11 AM UTC

   We are still working to resolve the issue affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will continue to provide updates as our work progresses.

7. identified Jun 30, 2026, 06:49 AM UTC

   We are still working to resolve the issue affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will continue to provide updates as our work progresses.

8. identified Jun 30, 2026, 11:20 AM UTC

   Additional capacity has been made available in the majority of regions, and we're seeing reduced failure rates in terms of project creation, project resizing, branch provisioning, and project restarts. We are still experiencing limited instance capacity in ap-northeast-2, ap-south-1, and eu-north-1. As a result, project operations that require capacity in these regions, including project creation, resizing, branch provisioning, restarts, may continue to fail. We are actively working to restore full capacity and will provide another update as soon as more information is available.

9. identified Jun 30, 2026, 06:58 PM UTC

   We are continuing to investigate the remaining capacity constraints affecting ap-northeast-2, ap-south-1, and eu-north-1. Project operations that require capacity in these regions may continue to fail. We will provide another update as soon as more information is available.

10. identified Jun 30, 2026, 10:22 PM UTC

    We are continuing to investigate the remaining capacity constraints affecting ap-northeast-2, ap-south-1, and eu-north-1. Project operations that require capacity in these regions may continue to fail. We will provide another update as soon as more information is available.

11. identified Jul 01, 2026, 03:23 AM UTC

    We are continuing to remediate the capacity constraints affecting multiple regions (ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, ap-southeast-2, eu-central-2, eu-north-1, sa-east-1, us-east-1, us-east-2). Project operations that require capacity in these regions may continue to fail or require a re-try. We will provide another update as soon as more information is available.

12. identified Jul 01, 2026, 10:12 AM UTC

    We continue to experience intermittent capacity related issues across all regions, impacting operations such as project creation, project resizing, branch provisioning, and project restarts. These operations may fail intermittently or require one or more retries to complete successfully. Our team is actively investigating ways to improve the situation and is implementing a number of mitigation measures to reduce the impact on affected operations. We will provide another update as soon as more information becomes available.

13. identified Jul 01, 2026, 04:58 PM UTC

    We continue to experience widespread capacity constraints across most regions, affecting project creation, project resizing, project restarts, branch provisioning, and restores. As a result, some users may experience repeated failures when attempting these operations. Our team is actively implementing mitigation measures to increase capacity and restore normal service. We will provide further updates as the situation evolves. If you're attempting to create a new project, we recommend waiting until the incident has progressed and the status page indicates that additional capacity has been made available before retrying. This issue does not affect existing running projects or their availability.

14. identified Jul 02, 2026, 01:30 AM UTC

    We continue to experience widespread capacity constraints across most regions, affecting project creation, project resizing, project restarts, branch provisioning, and restores. As a result, some users may experience repeated failures when attempting these operations. Our team is actively implementing mitigation measures to increase capacity and restore normal service. We will provide further updates as the situation evolves. If you're attempting to create a new project, we recommend waiting until the incident has progressed and the status page indicates that additional capacity has been made available before retrying. This issue does not affect existing projects or their availability unless the instance undergoes restarts, restores, or database upgrades.

15. identified Jul 02, 2026, 05:53 AM UTC

    We are seeing capacity improvements across all regions, but are continuing to work on a full mitigation for all users. Project creation, project resizing, project restarts, branch provisioning, and restores are slowly recovering and we are asking users to re-try their database actions. Please reach out to our Support if you continue to fail. Running projects are unaffected and stay available. The issue has only surfaced during a restart, restore, or database upgrade. We are still addressing an issue with Read Replicas and continuing to increase capacity to restore normal service in full with highest priority.

16. identified Jul 02, 2026, 10:40 AM UTC

    We continue to see capacity improvements across all regions and have implemented mitigation measures to sustain capacity. Project creation, resizing, restarts, branch revisioning, and restores are continuing to recover, and we ask users to retry their database actions. Please reach out to our support if you continue to see failures. Our team is actively working to restore the remaining affected projects. We will provide further updates as this work progresses. This issue does not affect existing projects or their availability unless the instance has undergone restarts with stores or database upgrades while the incident has been in progress

17. identified Jul 02, 2026, 03:08 PM UTC

    We continue to see capacity improvements across all regions and have implemented mitigation measures to sustain capacity. Project creation, resizing, restarts, and branch operations are continuing to recover, and we ask users to retry their database actions. Please reach out to our support if you continue to see failures. We are working to recover subset of projects which are still down due to infrastructure compatibility constraints. Our team is actively working on solutions to restore these remaining affected projects and will provide further updates as this work progresses. This issue does not affect existing projects or their availability unless the instance has undergone restarts or resizes while the incident has been in progress.

18. identified Jul 03, 2026, 09:43 AM UTC

    We currently have capacity available across all regions and are continuing to make progress on our remaining mitigation work, primarily by bringing additional capacity online. This is currently our top priority. We are also recovering a subset of projects which are still down due to infrastructure compatibility constraints. Our team is continuing to restore these remaining affected projects and will provide further updates as this work progresses. This issue does not affect existing projects or their availability unless the instance has undergone restarts or resizes while the incident has been in progress.

19. identified Jul 03, 2026, 04:03 PM UTC

    Capacity is currently available across all regions, and we are continuing to progress the remaining mitigation work, including bringing additional capacity online. This remains our highest priority. We have recovered most projects that were unavailable due to infrastructure compatibility constraints. Our team is continuing to restore the remaining affected projects and will provide further updates as this work progresses. The remaining impact is primarily limited to Medium instances running PostgreSQL versions earlier than 17.6.1.121. New project deployments should succeed, but restarts or resizes for projects matching this profile may fail. Existing projects are not affected unless they have been restarted or resized during this incident.

20. identified Jul 03, 2026, 07:57 PM UTC

    We're continuing to work through elevated capacity errors affecting some restart and resize operations. Availability for smaller compute sizes has improved across most regions, and error rates are trending down. Capacity for some smaller compute sizes remains constrained in a number of regions, most notably Medium. We are actively adding capacity across all regions to relieve this. If your project is on Postgres 17.6.1.121 or earlier, upgrading to 17.6.1.121 or higher gives it access to additional machine types, which improves the likelihood of a successful restart or resize in affected regions. You can check your current version and start an upgrade from your project's infrastructure settings: https://supabase.com/dashboard/project/_/settings/infrastructure If your project is affected and you're unable to resize or restart, our support team can help. We'll update this page as the situation materially changes.

21. identified Jul 04, 2026, 04:34 AM UTC

    Update - Availability for smaller compute sizes has improved across most regions, and error rates are trending down. We are continuing to monitor available capacity in all regions. If your project is on a version older than Postgres 17.6.1.121, upgrading to 17.6.1.121 and above will grant access to additional machine types, which improves the likelihood of a successful restart or resize. You can check your current version and start an upgrade from your project's infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure If your project is affected and you're unable to resize or restart, our support team can help. We'll update this page as the situation materially changes.

22. identified Jul 04, 2026, 10:40 PM UTC

    We are continuing to monitor available capacity in all regions. If your project is on a version older than Postgres 17.6.1.121, upgrading to 17.6.1.121 and above will grant access to additional machine types, which improves the likelihood of a successful restart or resize. You can check your current version and start an upgrade from your project's infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure If your project is affected and you're unable to resize or restart, our support team can help. We'll update this page as the situation materially changes.

23. identified Jul 06, 2026, 11:32 AM UTC

    Capacity has continued to recover across all regions, and the large majority of restart, resize, and project-creation operations are now completing normally. We are continuing to monitor the system. The remaining impact is limited to projects running a Postgres version older than 17.6.1.121. These older versions can only run on a narrower set of instance types, which are the ones still under capacity pressure, so a restart or resize may fail or need a retry. Projects on 17.6.1.121 or newer can run on a wider set of instance types and are much less likely to be affected. If a restart or resize is failing, upgrading to Postgres 17.6.1.121 or newer resolves it in most cases. You can check your current version and start an upgrade from your project's infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure If you're still unable to resize or restart after upgrading, our support team can help. We will update this page as the situation materially changes.

24. monitoring Jul 06, 2026, 04:36 PM UTC

    Capacity has continued to recover across all regions, and the large majority of restart, resize, and project-creation operations are now completing normally. We are continuing to monitor the system. We have added additional mitigations and machine types available to all Postgres versions, and we are also seeing error rates for these users stabilize. While there is still ongoing work behind the scenes to continue to improve our resiliency, users should no longer be affected by capacity issues stemming from this incident. We are showing stable capacity across all regions on all machine sizes and types. We will be monitoring this for the next day or two at least just to ensure the ongoing work is effective and we don't have any re-occurrence of these or similar issues before we resolve this entirely. If you continue to receive errors relating to capacity, please notify our support team via https://supabase.help and reference this status page.

25. monitoring Jul 08, 2026, 04:41 PM UTC

    We continue to monitor capacity recovery across all regions. Restart, resize, and project-creation operations are completing normally. We have added additional mitigations and machine types available to all Postgres versions, and we are also seeing error rates for these users stabilize. While there is still ongoing work behind the scenes to continue to improve our resiliency, users should no longer be affected by capacity issues stemming from this incident. We are showing stable capacity across all regions on all machine sizes and types. We will be monitoring this thru the rest of the week to ensure ongoing work is effective and we don't have any re-occurrence of these or similar issues before we resolve this entirely.

26. monitoring Jul 10, 2026, 06:41 PM UTC

    We continue to monitor capacity across all regions. The additional mitigations and machine types available to all Postgres versions are contributing to capacity stability. We continue to work to improve our resiliency. We will continue monitoring closely to ensure ongoing work is effective and we don't have any re-occurrence of these or similar issues before we resolve this entirely.

27. resolved Jul 13, 2026, 04:00 PM UTC

    Capacity availability and project creation, resize, and restart operations have returned to normal and have remained stable for an extended period of time. We are resolving this incident. Out of an abundance of caution, and out of respect for the impact this incident had for our users, we held the incident open for a considerable amount of time after the observed impact was mitigated. We wanted to be certain any residual potential impact was fully cleared before formally resolving the statuspage.

Read the full incident report →

Started Jun 25, 2026, 02:20 PM UTC· resolved Jun 25, 2026, 06:51 PM UTC

1. investigating Jun 25, 2026, 02:20 PM UTC

   We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps.

2. investigating Jun 25, 2026, 02:41 PM UTC

   Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays.

3. identified Jun 25, 2026, 03:01 PM UTC

   The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources.

4. identified Jun 25, 2026, 03:32 PM UTC

   We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades.

5. identified Jun 25, 2026, 04:03 PM UTC

   We are continuing to work through a variety of options for improving upgrade performance. This includes working with our upstream provider and adjusting operational parameters.

6. identified Jun 25, 2026, 04:27 PM UTC

   We are implementing operational mitigations to try to improve upgrade performance.

7. identified Jun 25, 2026, 05:03 PM UTC

   We are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems.

8. identified Jun 25, 2026, 05:46 PM UTC

   We are starting to notice improvements as a result of our mitigation efforts, and expect that project upgrades should start to become less delayed. We’ll continue monitoring and will update as we observe improvements across the fleet.

9. monitoring Jun 25, 2026, 06:08 PM UTC

   We have implemented all necessary mitigations and the project upgrade rates have returned to normal across the fleet. We will continue to monitor these flows for any irregularities or recurring degradation. If you are still experiencing delayed or blocked upgrades on your Project, please contact Support.

10. resolved Jun 25, 2026, 06:51 PM UTC

    Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved.

Read the full incident report →