Supabase Outage History

Started Sep 16, 2026, 08:10 AM UTC· resolved Sep 16, 2026, 09:33 AM UTC

1. identified Sep 16, 2026, 08:10 AM UTC

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

2. identified Sep 16, 2026, 09:06 AM UTC

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

3. monitoring Sep 16, 2026, 10:08 AM UTC

   We implemented a fix and are monitoring the system.

4. resolved Sep 16, 2026, 10:08 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 11, 2026, 05:00 PM UTC· resolved Sep 11, 2026, 05:00 PM UTC

1. resolved Sep 14, 2026, 06:08 PM UTC

   We observed latency issues over the weekend resulting in 504 errors primarily impacting customers on the Free tier. The incident has been resolved.

Read the full incident report →

Started Sep 10, 2026, 03:26 PM UTC· resolved Sep 11, 2026, 07:06 PM UTC

1. investigating Sep 10, 2026, 03:26 PM UTC

   We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.

2. identified Sep 10, 2026, 03:46 PM UTC

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

3. identified Sep 10, 2026, 05:13 PM UTC

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

4. identified Sep 10, 2026, 05:59 PM UTC

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

5. identified Sep 10, 2026, 07:41 PM UTC

   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.

6. monitoring Sep 11, 2026, 04:07 AM UTC

   We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Users still affected by project outages are encouraged to restart their projects which has shown to resolve lasting errors.

7. monitoring Sep 11, 2026, 07:07 AM UTC

   We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Due to this incident, impacted users who's project were compute constrained would have received a 'Your Supabase Project is running out of Disk IO Budget' email which is no longer valid. No further action is required and your project availability should be restored to normal.

8. resolved Sep 11, 2026, 07:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 09, 2026, 08:47 AM UTC· resolved Sep 09, 2026, 08:47 AM UTC

1. resolved Sep 09, 2026, 08:47 AM UTC

   Between 05:50–06:05 UTC some customer using Supavisor in us-east-1 may have experienced brief dropped connections or connection disruptions. This issue was caused by an unexpected restart of Supavisor instances in the affected cluster. We apologize for any disruption caused.

Read the full incident report →

Started Sep 04, 2026, 01:08 AM UTC· resolved Sep 04, 2026, 08:18 AM UTC

1. investigating Sep 04, 2026, 01:08 AM UTC

   We are seeing increased error rates in actions across all project lifecycle actions - Creations, Deletions, Restores, Configuration and Compute size upgrades. We are currently looking into the cause. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information

2. identified Sep 04, 2026, 01:08 AM UTC

   We have identified the source of the errors with project lifecycle actions, and the team is currently working to resolve it. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information.

3. identified Sep 04, 2026, 01:08 AM UTC

   The team has applied a fix, but error rates remain high. We are continuing to work and will take other necessary steps to resolve this as soon as possible. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved: Creates, Configuration changes, Restarts, or Compute size changes. We will provide additional updates as we have more information.

4. identified Sep 04, 2026, 02:10 AM UTC

   We are seeing incremental improvements internally. There is a large backlog of actions that we are working through, but things are progressing. Once we make it through most of the backlog, we will re-enable lifecycle actions. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

5. identified Sep 04, 2026, 02:10 AM UTC

   The team is continuing to work on restoring project lifecycle operations. Out of caution, we have disabled lifecycle operations. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected. We will provide additional updates as we have more information.

6. identified Sep 04, 2026, 03:05 AM UTC

   Error rates have returned to normal, and the backlogs are draining well. We are beginning to slowly re-enable lifecycle operations for users. We will be monitoring impact, and we hope to have this re-enabled everywhere soon. We will leave this in this state until lifecycle operations have been completely restored. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

7. identified Sep 04, 2026, 04:08 AM UTC

   We've increased project lifecycle operations to 50% of users and things are holding steady. We're continuing to ramp this up until operations are restored for all users. This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc. Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

8. monitoring Sep 04, 2026, 05:05 AM UTC

   Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal. We are going to monitor to ensure that things stay stable. The team is working through any remaining projects which did not automatically resolve. Some users may also notice that backups will happen a bit later than usual, but these jobs are running and completing normally.

9. resolved Sep 04, 2026, 08:18 AM UTC

   Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.

Read the full incident report →

Started Sep 01, 2026, 09:06 AM UTC· resolved Sep 01, 2026, 10:34 AM UTC

1. investigating Sep 01, 2026, 09:06 AM UTC

   We are currently investigating an issue where users are unable to login to the Supabase dashboard

2. investigating Sep 01, 2026, 09:06 AM UTC

   We’re investigating an issue preventing users from logging in to the Supabase Dashboard. Users who were logged into the dashboard were logged out. Dashboard actions are currently not available. Projects remain online and available. Non-Dashboard traffic is not impacted. We’ll share another update as soon as we have more information.

3. monitoring Sep 01, 2026, 10:06 AM UTC

   A recent change affected users ability to log in to the Supabase Dashboard. We’ve reverted the change, and testing indicates that the issue is resolved. Please try logging in again. If you’re still unable to log in, perform a full browser refresh and retry. Projects and non-Dashboard traffic remained unaffected.

4. resolved Sep 01, 2026, 11:06 AM UTC

   This incident has been resolved. Users should now be able to log in to the Supabase Dashboard normally. Projects and non-Dashboard traffic were unaffected throughout the incident.

Read the full incident report →

Started Aug 31, 2026, 04:28 PM UTC· resolved Aug 31, 2026, 07:06 PM UTC

1. investigating Aug 31, 2026, 04:28 PM UTC

   Project creation is failing for new projects on the platform. We are investigating.

2. investigating Aug 31, 2026, 04:53 PM UTC

   We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance.

3. investigating Aug 31, 2026, 05:20 PM UTC

   We continue to work this issue. The steps we have taken are addressing the hypothesized cause of the issue. We are implementing further related mitigations.

4. investigating Aug 31, 2026, 05:49 PM UTC

   While the first set of actions are taking effect, we are implementing a second set of likely mitigations to attempt to facilitate improvement in project creation.

5. identified Aug 31, 2026, 06:01 PM UTC

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

6. monitoring Aug 31, 2026, 06:29 PM UTC

   Project creation is reporting as recovered across the platform. We will monitor for stability in the near term.

7. resolved Aug 31, 2026, 07:06 PM UTC

   Project creation has returned to baseline consistently.

Read the full incident report →

Started Aug 28, 2026, 04:18 PM UTC· resolved Aug 28, 2026, 04:18 PM UTC

1. resolved Aug 28, 2026, 04:18 PM UTC

   PostgreSQL 15 projects were failing to load /usr/lib/postgresql/15/lib/supautils.so because GLIBC_2.33 is unavailable on affected hosts. This disrupted database access in multiple regions. Rollback is now complete and we are seeing access restored to projects in the affected regions.

Read the full incident report →

Started Aug 27, 2026, 05:20 PM UTC· resolved Aug 31, 2026, 03:57 PM UTC

1. investigating Aug 27, 2026, 05:20 PM UTC

   We’re currently investigating latency issue that may cause increased response times for a small percentage of requests. In some cases, this may also result in 525 errors. Our team is actively working to resolve the issue. We’ll share another update as soon as we have more information.

2. investigating Aug 27, 2026, 05:57 PM UTC

   We’re continuing to investigate the issue causing increased response times for requests and 525 errors. Our team remains actively engaged in the investigation, we’ll provide another update as soon as we have more details.

3. investigating Aug 27, 2026, 06:55 PM UTC

   We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.

4. investigating Aug 27, 2026, 08:37 PM UTC

   We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.

5. identified Aug 28, 2026, 02:08 AM UTC

   The team has identified the change which resulted in additional latency and error rates for some data API Requests. They are preparing to roll this change back. This rollout will take some time, and we will update again as there is news on the progress of the fix.

6. identified Aug 28, 2026, 02:09 PM UTC

   We are continuing to work through the remediation plan for the latency issues. We will provide a further update as soon as more information is available.

7. identified Aug 28, 2026, 05:21 PM UTC

   PostgREST 14.5 has been deployed since 12:00pm UTC to all AP regions: ap-east-1, ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, and ap-southeast-2 as well as sa-east-1 and ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-west-2, and eu-west-3, us-west-1 We'll continue to provide updates as we roll out the change for the remaining impacted regions.

8. identified Aug 28, 2026, 06:15 PM UTC

   The roll out has also been completed for us-east-1.

9. monitoring Aug 28, 2026, 09:06 PM UTC

   The rollout has been completed in all regions. We will continue to monitor.

10. monitoring Aug 29, 2026, 01:25 AM UTC

    Response times have recovered in all regions. We will continue to monitor throughout the weekend.

11. resolved Aug 31, 2026, 03:57 PM UTC

    Response times have recovered in all regions. This issue is now resolved.

Read the full incident report →

Started Aug 26, 2026, 07:49 PM UTC· resolved Aug 27, 2026, 06:24 PM UTC

1. investigating Aug 26, 2026, 07:49 PM UTC

   Some users on older Projects are experiencing a pgBouncer configuration issue causing connection issues for the Dedicated Pooler and Storage services. This issue should only affect users with Project versions 15.1 and older. We have determined the cause of this issue and we are rolling out a fix.

2. investigating Aug 26, 2026, 09:36 PM UTC

   Some users on Project versions 15.1 and older are experiencing a pgBouncer configuration issue causing connection issues for the Dedicated Pooler and Storage services. We are continuing our investigation of this issue.

3. identified Aug 27, 2026, 01:21 AM UTC

   This issue is fixed in eu-central-2 and ap-south-1. We are continuing to rollout the fix to all regions.

4. identified Aug 27, 2026, 11:09 AM UTC

   We are continuing to rollout the fix to further regions.

5. identified Aug 27, 2026, 01:06 PM UTC

   An enhanced automated solution is currently being tested in staging. It is expected to be more effective and efficient than the approach used previously. Once testing has completed successfully, we will use this approach to roll out the fix in production. We will provide further updates as this work progresses.

6. monitoring Aug 27, 2026, 05:07 PM UTC

   A fix has been rolled out across all regions, and results are positive. We will continue monitoring to ensure the service remains stable. Moving this incident to monitoring.

7. resolved Aug 27, 2026, 06:24 PM UTC

   The fix has remained stable across all regions, and the issue has been resolved.

Read the full incident report →

Started Aug 24, 2026, 03:26 PM UTC· resolved Aug 24, 2026, 04:38 PM UTC

1. investigating Aug 24, 2026, 03:26 PM UTC

   We are aware of reports of increased rates of connection timeouts for users connecting to Projects in us-east-1 via Supavisor.

2. monitoring Aug 24, 2026, 03:38 PM UTC

   We have identified a degraded Supavisor node and we have rolled out a fix. We are monitoring to ensure continued stability.

3. resolved Aug 24, 2026, 04:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 24, 2026, 01:52 PM UTC· resolved Aug 24, 2026, 03:53 PM UTC

1. investigating Aug 24, 2026, 01:52 PM UTC

   We are investigating an issue affecting automatic disk resizing. Some projects may experience delays before a resize is completed, while others may see repeated or duplicate resize operations. We are working to identify the cause and will provide an update as soon as we have more information.

2. monitoring Aug 24, 2026, 02:47 PM UTC

   A fix has been applied, and the issue is now resolved. We are moving the incident to monitoring. We will continue to follow up directly with affected users who opened a support ticket.

3. resolved Aug 24, 2026, 03:53 PM UTC

   The issue affecting automatic disk resizing has been resolved. We will continue to follow up directly with affected users who opened a support ticket.

Read the full incident report →

Started Aug 24, 2026, 06:02 AM UTC· resolved Aug 24, 2026, 09:51 AM UTC

1. investigating Aug 24, 2026, 06:02 AM UTC

   We are investigating error spikes in the ap-northeast-2 Supavisor clusters. Users reported failures in connecting to postgres via Supavisor with the error: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode.

2. investigating Aug 24, 2026, 07:07 AM UTC

   We are continuing to investigate the errors in ap-northeast-2 Supavisor clusters.

3. monitoring Aug 24, 2026, 09:13 AM UTC

   We have applied a fix and are monitoring for full resolution. Errors have ceased in the last minutes and all connections are back to healthy.

4. resolved Aug 24, 2026, 09:51 AM UTC

   The issue has been resolved.

Read the full incident report →

Started Aug 24, 2026, 05:39 AM UTC· resolved Aug 24, 2026, 05:39 AM UTC

1. resolved Aug 24, 2026, 05:39 AM UTC

   Between 04:54 and 04:58 UTC we observed error spikes in one of the eu-east-1 Supavisor clusters. Users would have experienced errors in connecting to postgres via Supavisor. The issue has since recovered. Errors reported: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode.

Read the full incident report →

Started Aug 21, 2026, 10:26 AM UTC· resolved Aug 21, 2026, 12:15 PM UTC

1. investigating Aug 21, 2026, 10:26 AM UTC

   We're investigating delays affecting project pause/restore, branch creation, and project provisioning across multiple regions. Some users may see failures or slowness when performing these operations. We'll share updates as we learn more.

2. identified Aug 21, 2026, 11:09 AM UTC

   We've identified the issue causing delays and failures in project pause/restore, branch creation, and project provisioning across multiple regions. Branch creation is currently failing for affected users, and project provisioning may be delayed. We're continuing to work on a fix and will share the next update as we have more information.

3. monitoring Aug 21, 2026, 11:35 AM UTC

   We've applied a fix for the issue affecting project pause/restore, branch creation, and project provisioning across multiple regions. Errors related to branch creation have dropped, and we're continuing to monitor to confirm full recovery. We'll share another update once we've confirmed the issue is resolved.

4. resolved Aug 21, 2026, 12:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 19, 2026, 03:57 PM UTC· resolved Aug 19, 2026, 04:10 PM UTC

1. investigating Aug 19, 2026, 03:57 PM UTC

   We have noticed connectivity issues for users in Myanmar. We are investigating.

Read the full incident report →

Started Aug 19, 2026, 03:52 PM UTC· resolved Sep 15, 2026, 12:48 PM UTC

1. investigating Aug 19, 2026, 03:52 PM UTC

   We are investigating reports that a limited number of users in Myanmar are unable to access Supabase. We will provide additional updates as information becomes available.

2. investigating Aug 19, 2026, 05:08 PM UTC

   The connectivity issues appear to be limited to a subset of ISPs in Myanmar. Impacted users could try alternative ISPs to restore connectivity while we work to address this issue.

3. identified Aug 20, 2026, 12:18 PM UTC

   We have reached out to the ISPs that have been involved in the connectivity challenges for users in Myanmar. We are continuing to work to address the issue.

4. identified Aug 25, 2026, 11:31 PM UTC

   We continue to reach out and make contact with the ISPs that have been involved in the connectivity challenges for some users in Myanmar. We are continuing to work to address the issue.

5. monitoring Sep 02, 2026, 07:05 PM UTC

   Supabase has taken the steps it can to address the blockage. We recommend customers contact their ISP for assistance: https://supabase.com/blog/navigating-regional-network-blocks

6. monitoring Sep 09, 2026, 06:29 PM UTC

   We continue to try to resolve this issue. We have made official requests for resolution to the appropriate parties in Myanmar.

7. resolved Sep 15, 2026, 12:48 PM UTC

   We have made a repeat reminder for resolution to the appropriate parties in Myanmar. As no further response has been received, this incident will be resolved. We recommend customers still experiencing issues to contact their ISP for assistance or review our workarounds proposed here: https://supabase.com/blog/navigating-regional-network-blocks

Read the full incident report →

Started Aug 19, 2026, 12:47 PM UTC· resolved Aug 19, 2026, 03:56 PM UTC

1. monitoring Aug 19, 2026, 12:47 PM UTC

   We've identified an issue causing sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects. Users authenticating with non-Google/Apple/Firebase OIDC providers may see failed login attempts. We've identified the root cause and fix has been rolled out. Impacted timeframe was 18th August 4pm UTC - 19th Aug 10:30am UTC

2. monitoring Aug 19, 2026, 12:48 PM UTC

   We've identified that starting 4pm UTC on August 18th we began seeing sign-in failures with signInWithIdToken (OIDC) logins on free-tier projects. Users authenticating with OIDC providers other than Google/Apple/Firebase may have seen failed login attempts. We've identified the root cause and fix has been rolled out.

3. monitoring Aug 19, 2026, 01:01 PM UTC

   We've identified that starting 4pm UTC on August 18th we began seeing sign-in failures with signInWithIdToken (OIDC) logins on free-tier projects. Users authenticating with OIDC providers other than Google/Apple/Firebase may have seen failed login attempts. We've identified the root cause and fix has been rolled out. We are monitoring for continued stability.

4. resolved Aug 19, 2026, 03:56 PM UTC

   We have confirmed that the fix has been effective and are marking this incident as resolved.

Read the full incident report →

Started Aug 17, 2026, 01:47 AM UTC· resolved Aug 17, 2026, 01:56 AM UTC

1. investigating Aug 17, 2026, 01:47 AM UTC

   We are investigating an issue with project creation failing. We will be confirming more information shortly.

2. resolved Aug 17, 2026, 01:56 AM UTC

   We have identified this as a non-user impacting alert and as such this is being resolved.

Read the full incident report →

Started Aug 14, 2026, 09:31 AM UTC· resolved Aug 14, 2026, 10:44 AM UTC

1. identified Aug 14, 2026, 09:31 AM UTC

   We are investigating an issue of project creation and updating in us-east-2. A fix is under review and prepared for being rolled out.

2. identified Aug 14, 2026, 09:49 AM UTC

   A fix is being rolled out and we are seeing improved performance across impacted projects. We are continuing to roll out the full fix and will be confirming recovery asap.

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

   A fix has been applied to all impacted projects in us-east-2. We are monitoring for full resolution.

4. resolved Aug 14, 2026, 10:44 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 14, 2026, 02:23 AM UTC· resolved Sep 29, 2026, 06:46 PM UTC

1. identified Aug 14, 2026, 02:23 AM UTC

   We have identified the root cause of newly refreshed JWTs being rejected by the API, resulting in HTTP 401 errors for affected sessions. We are working on a fix and will provide updates as things progress.

2. identified Aug 14, 2026, 07:53 AM UTC

   Our teams are continuing to work on the fix and rollout is underway for selected customers. We will provide another update as we are applying the fix to all impacted users.

3. identified Aug 18, 2026, 06:38 PM UTC

   Fixes for this issue are being sequentially rolled out. The impact of the issue is limited to a subset of new projects that can experience it upon some JWT renewals. We will update the status when all the fix rollouts have completed.

4. identified Aug 20, 2026, 04:37 PM UTC

   As part of the incident remediation flow, we have separately identified "/lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found" error between 11:15 - 16:24 UTC today affecting PostgREST. This has been fixed and we can see the error rates have subsided.

5. identified Aug 21, 2026, 05:21 PM UTC

   We are continuing to test and rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful. We will monitor eu-central-2 over the weekend and are preparing for the fix to be pushed to all regions starting Monday. Thank you for your patience while we've worked on multiple fixes for this issue.

6. identified Aug 25, 2026, 06:41 PM UTC

   We are continuing to rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful. This fix has been applied to the following regions: ap-east-1 ap-northeast-1 ap-northeast-2 ap-south-1 ap-southeast-1 ap-southeast-2 ca-central-1 eu-central-1 eu-central-2 eu-north-1 eu-west-2 eu-west-3 We will continue rolling out this fix to the remaining regions throughout this week and provide updates as more regions are successful.

7. identified Aug 27, 2026, 05:17 PM UTC

   PostgREST 14.17 has now been rolled out to all regions. Some customers have reported that restarting their project after the rollout resolved this issue. To restart your project, go to the General settings page in the dashboard and select Restart project. Please contact our support team if the issue persists after a restart.

8. identified Aug 28, 2026, 11:44 PM UTC

   We continue to monitor the fixes introduced by this latest rollout. If you are continuing to see these errors, some customers have reported that restarting their project after the rollout resolved this issue. To restart your project, go to the General settings page in the dashboard and select Restart project. Please contact our support team if the issue persists after a restart.

9. identified Aug 31, 2026, 07:52 PM UTC

   We have seen reports that the JWT rejection issue persisted with 14.17, and due to some unintended performance side effects, we have rolled back to Postgrest 14.5. The team continues to investigate the JWT issue and hopes to have a solution soon.

10. identified Sep 02, 2026, 07:38 PM UTC

    A stale time cache has been identified as the cause of this issue. A targeted fix has been written and is undergoing internal testing. It will be rolled out when testing is complete. Thank you for your patience while we investigated this issue. We will update the status page when the fix is rolled out.

11. identified Sep 07, 2026, 09:49 AM UTC

    Testing results have been positive. Following some additional checks today, we plan to expand the rollout. We’ll continue to monitor progress and provide further updates as they become available.

12. identified Sep 11, 2026, 11:41 PM UTC

    We continue to monitor progress and are slowly updating each region. Thank you for your patience on this issue.

13. identified Sep 17, 2026, 07:30 PM UTC

    To resolve this issue, our fleet requires a change to our deploy process. We have spent this week making these changes and will be implementing them throughout this weekend, starting on Friday, September 18. Once this change is implemented, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue. We recognize that this is added work for our customers. This issue has been open for over a month, as we tried to make this change on each project's behalf. In an effort to resolve this sooner, we have opted to make this deployment process change and ask users to upgrade.

14. identified Sep 23, 2026, 07:26 AM UTC

    We have rolled out the deployment process changes to eu-central-2 and continue to monitor. We will provide additional updates as we make this change to other regions. Once this change is implemented across all regions, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue.

15. identified Sep 25, 2026, 04:23 PM UTC

    The deployment process changes have been rolled out across all regions. We will monitor throughout the weekend. The new Supabase version will be released early next week. Once it is released, impacted users can upgrade to from their dashboard to resolve this issue. Thank you again for your patience while we worked through this. We will provide an update once the new version is available and users can upgrade.

16. resolved Sep 29, 2026, 06:46 PM UTC

    The latest Supabase version has been released. All users impacted by this issue can now upgrade from the dashboard to resolve this issue. Since this new version is released, we will resolve this issue. If you have any questions about upgrading, please refer to our documentation for more information: https://supabase.com/docs/guides/platform/upgrading Thank you again for your patience while we worked on resolving this issue.

Read the full incident report →

Started Aug 11, 2026, 02:37 PM UTC· resolved Aug 11, 2026, 06:30 PM UTC

1. investigating Aug 11, 2026, 02:37 PM UTC

   We're currently investigating an issue that is impacting MCP connections to branch environments.

2. identified Aug 11, 2026, 03:09 PM UTC

   We've identified the root cause that was leading to permission errors on MCP connections to branch environments. We're currently working on addressing this.

3. identified Aug 11, 2026, 03:52 PM UTC

   We're still working on implementing a fix for the identified root cause.

4. monitoring Aug 11, 2026, 04:33 PM UTC

   We have pushed a fix to address the root cause and are monitoring the situation. If you continue to see an error, you can re-authenticate with the Supabase MCP server and also confirm that you have access to the preview branch.

5. monitoring Aug 11, 2026, 05:48 PM UTC

   We have pushed a fix to address the root cause and are monitoring the situation. If you continue to see an error, you can re-authenticate with the Supabase MCP server and also confirm that you have access to the preview branch.

6. resolved Aug 11, 2026, 06:30 PM UTC

   Customers should now be able to connect to branch environments via MCP normally.

Read the full incident report →

Started Aug 03, 2026, 03:28 PM UTC· resolved Aug 05, 2026, 05:33 PM UTC

1. investigating Aug 03, 2026, 03:28 PM UTC

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

2. investigating Aug 03, 2026, 04:19 PM UTC

   We are continuing to investigate project upgrade issues.

3. identified Aug 03, 2026, 05:09 PM UTC

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

4. identified Aug 03, 2026, 07:47 PM UTC

   We are developing a fix for the upgrade issues.

5. identified Aug 03, 2026, 10:46 PM UTC

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

6. identified Aug 04, 2026, 03:30 PM UTC

   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.

7. identified Aug 04, 2026, 11:38 PM UTC

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

8. monitoring Aug 05, 2026, 02:58 PM UTC

   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.

9. resolved Aug 05, 2026, 05:33 PM UTC

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

Read the full incident report →

Started Jul 31, 2026, 06:36 PM UTC· resolved Aug 04, 2026, 08:00 PM UTC

1. identified Jul 31, 2026, 06:36 PM UTC

   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.

2. identified Jul 31, 2026, 08:49 PM UTC

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

3. identified Jul 31, 2026, 09:41 PM UTC

   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.

4. identified Jul 31, 2026, 10:55 PM UTC

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

5. monitoring Aug 01, 2026, 01:19 AM UTC

   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.

6. monitoring Aug 03, 2026, 10:36 PM UTC

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

7. resolved Aug 04, 2026, 08:00 PM UTC

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

Read the full incident report →

Started Jul 31, 2026, 12:27 PM UTC· resolved Jul 31, 2026, 01:26 PM UTC

1. investigating Jul 31, 2026, 12:27 PM UTC

   We're investigating issues updating DNS records for newly created, unpaused, or updated databases.

2. identified Jul 31, 2026, 12:41 PM UTC

   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.

3. monitoring Jul 31, 2026, 12:55 PM UTC

   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.

4. resolved Jul 31, 2026, 01:26 PM UTC

   The incident has been resolved.

Read the full incident report →