Aug <var data-var='date'>17</var>, <var data-var='time'>01:56</var> UTC Resolved - We have identified this as a non-user impacting alert and as such this is being resolved. Aug <var data-var='date'>17</var>, <var data-var='time'>01:47</var> UTC Investigating - We are investigating an issue with project creation failing. We will be confirming more information shortly.

Project creation failing in selected regions

Aug <var data-var='date'>14</var>, <var data-var='time'>10:44</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>14</var>, <var data-var='time'>09:59</var> UTC Monitoring - A fix has been applied to all impacted projects in us-east-2. We are monitoring for full resolution. Aug <var data-var='date'>14</var>, <var data-var='time'>09:49</var> UTC Update - 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. Aug <var data-var='date'>14</var>, <var data-var='time'>09:31</var> UTC Identified - 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.

Project access, updating and creation impacted in us-east-2

Aug <var data-var='date'>14</var>, <var data-var='time'>07:53</var> UTC Update - 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. Aug <var data-var='date'>14</var>, <var data-var='time'>02:23</var> UTC Identified - 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.

401 errors due to JWT rejections

Aug <var data-var='date'>11</var>, <var data-var='time'>18:30</var> UTC Resolved - Customers should now be able to connect to branch environments via MCP normally. Aug <var data-var='date'>11</var>, <var data-var='time'>17:48</var> UTC Update - 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. Aug <var data-var='date'>11</var>, <var data-var='time'>16:33</var> UTC Monitoring - UPDATE: We are currently pushing a fix to address the root cause. We'll provide another update once the fix has been fully deployed. Aug <var data-var='date'>11</var>, <var data-var='time'>15:52</var> UTC Update - We're still working on implementing a fix for the identified root cause. Aug <var data-var='date'>11</var>, <var data-var='time'>15:09</var> UTC Identified - 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. Aug <var data-var='date'>11</var>, <var data-var='time'>14:37</var> UTC Investigating - We're currently investigating an issue that is impacting MCP connections to branch environments.

MCP connection error to branch environments

Aug <var data-var='date'> 5</var>, <var data-var='time'>17:33</var> UTC Resolved - Project upgrades have remained stable, we are resolving this incident. Aug <var data-var='date'> 5</var>, <var data-var='time'>14:58</var> UTC Monitoring - 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. Aug <var data-var='date'> 4</var>, <var data-var='time'>23:38</var> UTC Update - We are continuing to test the fix to project upgrades. We will update again when the fix is applied. Aug <var data-var='date'> 4</var>, <var data-var='time'>15:30</var> UTC Update - 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. Aug <var data-var='date'> 3</var>, <var data-var='time'>22:46</var> UTC Update - We are continuing to fix project upgrade issues and are investigating further remediation. We will provide our next update within the next 14 hours. Aug <var data-var='date'> 3</var>, <var data-var='time'>19:47</var> UTC Update - We are developing a fix for the upgrade issues. Aug <var data-var='date'> 3</var>, <var data-var='time'>17:09</var> UTC Identified - We have identified the cause of the upgrade delays and are working on a fix. Aug <var data-var='date'> 3</var>, <var data-var='time'>16:19</var> UTC Update - We are continuing to investigate project upgrade issues. Aug <var data-var='date'> 3</var>, <var data-var='time'>15:28</var> UTC Investigating - We are investigating a potential issue that could result in a delay or failure in some users' project upgrades.

Project Upgrade Delays

Aug <var data-var='date'> 4</var>, <var data-var='time'>20:00</var> UTC Resolved - After monitoring, we have confirmed that issues affecting Management API performance have been resolved. Aug <var data-var='date'> 3</var>, <var data-var='time'>22:36</var> UTC Update - We are continuing to monitor the the Management API to ensure no further intermittent occurrences appear. We will provide another update within 24 hours. Aug <var data-var='date'> 1</var>, <var data-var='time'>01:19</var> UTC Monitoring - 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. Jul <var data-var='date'>31</var>, <var data-var='time'>22:55</var> UTC Update - We are continuing mitigation efforts for the intermittent issues with the Management API. Jul <var data-var='date'>31</var>, <var data-var='time'>21:41</var> UTC Update - 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. Jul <var data-var='date'>31</var>, <var data-var='time'>20:49</var> UTC Update - We've isolated the cause of the network issues with the Management API and we are working on a fix. Jul <var data-var='date'>31</var>, <var data-var='time'>18:36</var> UTC Identified - 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.

Management API Performance Degradation

Jul <var data-var='date'>31</var>, <var data-var='time'>13:26</var> UTC Resolved - The incident has been resolved. Jul <var data-var='date'>31</var>, <var data-var='time'>12:55</var> UTC Monitoring - 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. Jul <var data-var='date'>31</var>, <var data-var='time'>12:41</var> UTC Identified - 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. Jul <var data-var='date'>31</var>, <var data-var='time'>12:27</var> UTC Investigating - We're investigating issues updating DNS records for newly created, unpaused, or updated databases.

DNS creation delays

Jul <var data-var='date'>31</var>, <var data-var='time'>13:20</var> UTC Resolved - 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. Jul <var data-var='date'>31</var>, <var data-var='time'>09:36</var> UTC Identified - 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. Jul <var data-var='date'>31</var>, <var data-var='time'>03:13</var> UTC Monitoring - Our fix has completed rollout and we are monitoring for full resolution. Jul <var data-var='date'>31</var>, <var data-var='time'>00:26</var> UTC Identified - The issue has been identified and a fix is being implemented. Jul <var data-var='date'>30</var>, <var data-var='time'>23:40</var> UTC Update - 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. Jul <var data-var='date'>30</var>, <var data-var='time'>22:21</var> UTC Update - 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. Jul <var data-var='date'>30</var>, <var data-var='time'>21:02</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'>30</var>, <var data-var='time'>19:46</var> UTC Update - 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. Jul <var data-var='date'>30</var>, <var data-var='time'>18:28</var> UTC Update - 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. Jul <var data-var='date'>30</var>, <var data-var='time'>18:16</var> UTC Update - Only a subset of users appear to be impacted by the issue with Edge Function deployments. We are investigating the root cause. Jul <var data-var='date'>30</var>, <var data-var='time'>17:37</var> UTC Investigating - We are aware of some users experiencing issues with Edge Function deployments.

Issues with Edge Function Deployment

Jul <var data-var='date'>31</var>, <var data-var='time'>02:42</var> UTC Resolved - The intermittent networking issues have subsided. Management-api is operating normally now. Jul <var data-var='date'>31</var>, <var data-var='time'>00:30</var> UTC Monitoring - The intermittent networking issues have subsided. Management-api is operating normally now. We will continue to monitor for abnormal behavior. Jul <var data-var='date'>30</var>, <var data-var='time'>22:54</var> UTC Update - We are continuing to investigate the issue. We will provide further updates as progress is made. Jul <var data-var='date'>30</var>, <var data-var='time'>21:58</var> UTC Update - We have identified some anomalies that appear correlated to this issue and we are continuing to investigate. Jul <var data-var='date'>30</var>, <var data-var='time'>21:19</var> UTC Update - We are continuing to investigate the issue. Jul <var data-var='date'>30</var>, <var data-var='time'>20:51</var> UTC Investigating - 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.

Jul <var data-var='date'>30</var>, <var data-var='time'>21:50</var> UTC Resolved - The issue has been resolved, and customers should now see new logs appearing as expected. Jul <var data-var='date'>30</var>, <var data-var='time'>21:39</var> UTC Monitoring - Log ingestion has been restored, and new logs are now appearing as expected. We will continue monitoring to ensure the issue is fully resolved. Jul <var data-var='date'>30</var>, <var data-var='time'>21:33</var> UTC Identified - 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. Jul <var data-var='date'>30</var>, <var data-var='time'>20:57</var> UTC Investigating - We are experiencing a problem with log ingestion. Customers may experience a lack of new logs being visible from their projects. We are investigating.

Log Ingestion Issues

Jul <var data-var='date'>28</var>, <var data-var='time'>22:07</var> UTC Resolved - 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. Jul <var data-var='date'>28</var>, <var data-var='time'>21:53</var> UTC Monitoring - 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. Jul <var data-var='date'>28</var>, <var data-var='time'>21:33</var> UTC Identified - 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. Jul <var data-var='date'>28</var>, <var data-var='time'>21:24</var> UTC Investigating - 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.

SSO login failures in us-east-1

Jul <var data-var='date'>28</var>, <var data-var='time'>14:13</var> UTC Resolved - Documentation search functionality has been restored. Jul <var data-var='date'>28</var>, <var data-var='time'>14:06</var> UTC Identified - 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.

Documents Search Unavailable

Jul <var data-var='date'>27</var>, <var data-var='time'>22:36</var> UTC Resolved - 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. Jul <var data-var='date'>27</var>, <var data-var='time'>22:23</var> UTC Monitoring - 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. Jul <var data-var='date'>27</var>, <var data-var='time'>20:53</var> UTC Update - 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. Jul <var data-var='date'>27</var>, <var data-var='time'>20:39</var> UTC Identified - 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. Jul <var data-var='date'>27</var>, <var data-var='time'>20:34</var> UTC Investigating - We are investigating failures in provisioning DNS records for projects, there may be delays in creation of DNS records for new or unpaused projects.

Delays in creation of DNS records

Jul <var data-var='date'>27</var>, <var data-var='time'>20:47</var> UTC Resolved - Project resizing has maintained expected performance in us-west-2. Jul <var data-var='date'>27</var>, <var data-var='time'>19:01</var> UTC Monitoring - 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. Jul <var data-var='date'>27</var>, <var data-var='time'>18:11</var> UTC Identified - We have identified the cause of the resize issues and are evaluating options for mitigating the problem. Jul <var data-var='date'>27</var>, <var data-var='time'>17:53</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'>27</var>, <var data-var='time'>17:42</var> UTC Investigating - We have noticed an issue with project resizing in us-west-2 and are investigating.

Project Resize Problems in US-West-2

Jul <var data-var='date'>25</var>, <var data-var='time'>14:45</var> UTC Resolved - Authentication operations have returned to normal consistently. Jul <var data-var='date'>25</var>, <var data-var='time'>14:25</var> UTC Monitoring - Authentication has returned to normal. Jul <var data-var='date'>25</var>, <var data-var='time'>14:21</var> UTC Identified - We have implemented a fix to the authentication issue and are monitoring for recovery. Jul <var data-var='date'>25</var>, <var data-var='time'>14:11</var> UTC Investigating - Some projects are experiencing authentication issues. We are actively investigating.

Authentication issues for some projects

Jul <var data-var='date'>23</var>, <var data-var='time'>11:30</var> UTC Resolved - Between 11:34 and 11:43 UTC, some projects 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.

Between 11:34 and 11:43 UTC, some projects in the us-east-2 (Ohio) region experienced degraded connectivity during a connection pooler maintenance upgrade

Jul <var data-var='date'>22</var>, <var data-var='time'>20:10</var> UTC Resolved - This issue is now resolved. Log ingestion has returned to normal and customers can now view project logs. Jul <var data-var='date'>22</var>, <var data-var='time'>18:40</var> UTC Update - We are continuing to monitor log ingestion to ensure it remains stable. Jul <var data-var='date'>22</var>, <var data-var='time'>17:49</var> UTC Monitoring - We have implemented a fix, and log ingestion has returned to normal. We will continue to monitor this issue to ensure it stays stable. Jul <var data-var='date'>22</var>, <var data-var='time'>16:56</var> UTC Identified - We have identified the issue and are working to re-enable the ingestion of logs. Jul <var data-var='date'>22</var>, <var data-var='time'>16:29</var> UTC Investigating - We are experiencing a problem with log ingestion. Customers may experience a lack of new logs being visible from their projects. We are investigating.

Log Ingestion Problems

Jul <var data-var='date'>18</var>, <var data-var='time'>01:41</var> UTC Resolved - Project actions have been sustained at normal performance. This incident is resolved. Jul <var data-var='date'>17</var>, <var data-var='time'>20:21</var> UTC Monitoring - 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. Jul <var data-var='date'>17</var>, <var data-var='time'>19:45</var> UTC Identified - We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results. Jul <var data-var='date'>17</var>, <var data-var='time'>19:20</var> UTC Update - We are testing mitigation options to attempt to restore project action performance. Jul <var data-var='date'>17</var>, <var data-var='time'>18:47</var> UTC Update - 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. Jul <var data-var='date'>17</var>, <var data-var='time'>18:16</var> UTC Update - 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. Jul <var data-var='date'>17</var>, <var data-var='time'>17:49</var> UTC Investigating - Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.

Project Actions Failing Across Multiple Regions

Jul <var data-var='date'>16</var>, <var data-var='time'>18:49</var> UTC Resolved - 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. Jul <var data-var='date'>16</var>, <var data-var='time'>18:32</var> UTC Update - We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress Jul <var data-var='date'>16</var>, <var data-var='time'>18:23</var> UTC Update - A likely mitigation has been identified and we are discussing the proper implementation method. Jul <var data-var='date'>16</var>, <var data-var='time'>17:55</var> UTC Identified - 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.

S3 endpoints for keys with special characters broken

Jul <var data-var='date'>16</var>, <var data-var='time'>11:35</var> UTC Resolved - 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. Jul <var data-var='date'>16</var>, <var data-var='time'>10:14</var> UTC Monitoring - 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. Jul <var data-var='date'>16</var>, <var data-var='time'>09:16</var> UTC Update - 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. Jul <var data-var='date'>16</var>, <var data-var='time'>07:42</var> UTC Update - 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. Jul <var data-var='date'>16</var>, <var data-var='time'>07:02</var> UTC Update - We are continuing to work on a fix for this issue. Jul <var data-var='date'>16</var>, <var data-var='time'>07:00</var> UTC Identified - 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.

Projects in stuck state in EU-CENTRAL-1 (Frankfurt)

Jul <var data-var='date'>15</var>, <var data-var='time'>00:50</var> UTC Resolved - This issue has been resolved. Jul <var data-var='date'>15</var>, <var data-var='time'>00:34</var> UTC Monitoring - 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. Jul <var data-var='date'>15</var>, <var data-var='time'>00:25</var> UTC Identified - We have identified the issue and are actively working on a fix. We will share another update as soon as we have more information. Jul <var data-var='date'>15</var>, <var data-var='time'>00:04</var> UTC Investigating - We are currently investigating an issue affecting the ability to view and manage authentication providers in the Supabase dashboard.

Errors configuring authentication providers

Jul <var data-var='date'>14</var>, <var data-var='time'>05:14</var> UTC Completed - The maintenance has been completed successfully. Jul <var data-var='date'>14</var>, <var data-var='time'>04:43</var> UTC Verifying - The deployment has finalised and we are monitoring our systems for issues. Jul <var data-var='date'>14</var>, <var data-var='time'>04:00</var> UTC Update - Scheduled maintenance is currently in progress. We are working to validate the final stages of the deployment and have extended the maintenance window to 04:30 UTC. Impact: - Various platform operations will be delayed during this window - These may include project creation and initial configuration/setup - All affected operations will be rescheduled at the end of the window to ensure no operation is dropped Jul <var data-var='date'>14</var>, <var data-var='time'>03:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jul <var data-var='date'> 1</var>, <var data-var='time'>17:06</var> UTC Scheduled - We will be carrying out a scheduled maintenance window to perform internal platform improvements and upgrades. Maintenance Window: - Start time: 03:00 UTC on July 14, 2026 - End time: 04:00 UTC on July 14, 2026 Impact: - Various platform operations will be delayed during this window - These may include project creation and initial configuration/setup - All affected operations will be rescheduled at the end of the window to ensure no operation is dropped

Scheduled Platform Maintenance July 14th, 2026

Jul <var data-var='date'>13</var>, <var data-var='time'>16:00</var> UTC Resolved - 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. Jul <var data-var='date'>10</var>, <var data-var='time'>18:41</var> UTC Update - 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. Jul <var data-var='date'> 8</var>, <var data-var='time'>16:41</var> UTC Update - We continue to monitor capacity recovery across all regions. 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. Jul <var data-var='date'> 6</var>, <var data-var='time'>16:36</var> UTC Monitoring - 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. Jul <var data-var='date'> 6</var>, <var data-var='time'>11:32</var> UTC Update - 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. Jul <var data-var='date'> 4</var>, <var data-var='time'>22:40</var> UTC Update - 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. Jul <var data-var='date'> 4</var>, <var data-var='time'>04:34</var> UTC Update - 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. Jul <var data-var='date'> 3</var>, <var data-var='time'>19:57</var> UTC Update - 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. Jul <var data-var='date'> 3</var>, <var data-var='time'>16:03</var> UTC Update - 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. Jul <var data-var='date'> 3</var>, <var data-var='time'>09:43</var> UTC Update - 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. Jul <var data-var='date'> 2</var>, <var data-var='time'>15:08</var> UTC Update - 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. Jul <var data-var='date'> 2</var>, <var data-var='time'>10:40</var> UTC Update - 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 Jul <var data-var='date'> 2</var>, <var data-var='time'>05:53</var> UTC Update - 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. Jul <var data-var='date'> 2</var>, <var data-var='time'>01:30</var> UTC Update - 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. Jul <var data-var='date'> 1</var>, <var data-var='time'>16:58</var> UTC Update - 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. Jul <var data-var='date'> 1</var>, <var data-var='time'>10:12</var> UTC Update - 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. Jul <var data-var='date'> 1</var>, <var data-var='time'>03:23</var> UTC Update - 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. Jun <var data-var='date'>30</var>, <var data-var='time'>22:22</var> UTC Update - 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. Jun <var data-var='date'>30</var>, <var data-var='time'>18:58</var> UTC Update - 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. Jun <var data-var='date'>30</var>, <var data-var='time'>11:20</var> UTC Update - 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. Jun <var data-var='date'>30</var>, <var data-var='time'>06:49</var> UTC Update - 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. Jun <var data-var='date'>30</var>, <var data-var='time'>05:11</var> UTC Update - 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. Jun <var data-var='date'>30</var>, <var data-var='time'>04:32</var> UTC Update - We are continuing to work on a fix for the issue and will provide updates as more information is available. Jun <var data-var='date'>30</var>, <var data-var='time'>03:38</var> UTC Identified - 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. Jun <var data-var='date'>30</var>, <var data-var='time'>03:08</var> UTC Update - 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. Jun <var data-var='date'>30</var>, <var data-var='time'>02:43</var> UTC Update - Project creation is impacted across multiple regions, we are investigating the root cause. Jun <var data-var='date'>30</var>, <var data-var='time'>02:38</var> UTC Investigating - We are currently investigating an issue affecting project creation in multiple regions.

Project status change failures in multiple regions

Jul <var data-var='date'>10</var>, <var data-var='time'>03:48</var> UTC Resolved - 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. Jul <var data-var='date'>10</var>, <var data-var='time'>03:03</var> UTC Monitoring - 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. Jul <var data-var='date'>10</var>, <var data-var='time'>02:53</var> UTC Identified - 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. Jul <var data-var='date'>10</var>, <var data-var='time'>01:25</var> UTC Update - 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. Jul <var data-var='date'>10</var>, <var data-var='time'>00:36</var> UTC Update - 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. Jul <var data-var='date'>10</var>, <var data-var='time'>00:02</var> UTC Update - 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. Jul <var data-var='date'> 9</var>, <var data-var='time'>23:34</var> UTC Investigating - We are currently investigating an issue affecting log ingestion across all regions. During this time, some logs may be delayed or unavailable.

Degraded log ingestion

Jul <var data-var='date'> 8</var>, <var data-var='time'>19:57</var> UTC Resolved - Edge function operations are normal. Jul <var data-var='date'> 8</var>, <var data-var='time'>19:28</var> UTC Monitoring - A rollback mitigation implemented by our team has addressed the problem. Edge functions have returned to normal. We will continue to monitor performance. Jul <var data-var='date'> 8</var>, <var data-var='time'>19:16</var> UTC Identified - 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. Jul <var data-var='date'> 8</var>, <var data-var='time'>18:37</var> UTC Investigating - We are aware of reports of elevated legacy JWT authorization errors on edge functions in some regions

Is Supabase down?

Supabase status is DEGRADED

Components with issues

Lastest published events

Project creation failing in selected regions

Project access, updating and creation impacted in us-east-2

401 errors due to JWT rejections

Supabase Services, Components and Regions

Recent Supabase events

Project creation failing in selected regions

Project access, updating and creation impacted in us-east-2

401 errors due to JWT rejections

MCP connection error to branch environments

Project Upgrade Delays

Management API Performance Degradation