THIS IS A SCHEDULED EVENT Jul <var data-var='date'>14</var>, <var data-var='time'>03:00</var> - <var data-var='time'>04:00</var> UTC 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'> 6</var>, <var data-var='time'>16:10</var> UTC Resolved - Operations have returned to normal. We are implementing improvements to prevent similar recurrences in the future. Jul <var data-var='date'> 6</var>, <var data-var='time'>15:42</var> UTC Monitoring - The fix has been applied and there are improvements to the error rates. We are continuing to work on ensuring the underlying issue does not recur. Jul <var data-var='date'> 6</var>, <var data-var='time'>15:15</var> UTC Identified - We have identified the cause of the 500 errors and are implementing a fix. Jul <var data-var='date'> 6</var>, <var data-var='time'>15:10</var> UTC Update - The scope of the errors is across regions in the Americas. We are narrowing down the likely causal chains. Jul <var data-var='date'> 6</var>, <var data-var='time'>14:47</var> UTC Update - The 500 errors are limited to us-east-1, we are actively exploring causes. Jul <var data-var='date'> 6</var>, <var data-var='time'>14:45</var> UTC Investigating - Multiple endpoints are returning 500 Internal server errors across our platform. We are investigating what has caused these errors.

Endpoints in Americas regions returning 500 Internal server error

Jul <var data-var='date'> 3</var>, <var data-var='time'>04:51</var> UTC Resolved - The project creation in ca-central-1 has been restored. Jul <var data-var='date'> 3</var>, <var data-var='time'>02:56</var> UTC Monitoring - We have restored project creation startup time in ca-central-1 and are monitoring the situation for full recovery. Jul <var data-var='date'> 3</var>, <var data-var='time'>02:13</var> UTC Update - 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. Jul <var data-var='date'> 3</var>, <var data-var='time'>00:26</var> UTC Update - 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. Jul <var data-var='date'> 2</var>, <var data-var='time'>23:35</var> UTC Identified - We have identified the root cause and are working on a fix. Jul <var data-var='date'> 2</var>, <var data-var='time'>22:59</var> UTC Investigating - 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.

Degraded project creation success rates in the ca-central-1 region

Jul <var data-var='date'> 2</var>, <var data-var='time'>17:14</var> UTC Resolved - This issue is resolved and advisor results are now available in the Dashboard. Jul <var data-var='date'> 2</var>, <var data-var='time'>16:53</var> UTC Monitoring - We've deployed the fix and are now monitoring the issue. Jul <var data-var='date'> 2</var>, <var data-var='time'>15:42</var> UTC Update - 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. Jul <var data-var='date'> 2</var>, <var data-var='time'>14:26</var> UTC Identified - 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.

Errors when attempting to view advisor results in the Supabase dashboard

Jul <var data-var='date'> 1</var>, <var data-var='time'>19:04</var> UTC Resolved - We've rolled out a fix for the R2NP issue, and users should be able to execute the flow again. Jul <var data-var='date'> 1</var>, <var data-var='time'>15:16</var> UTC Identified - 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.

Issues with Restore to New Project

Jul <var data-var='date'> 1</var>, <var data-var='time'>18:56</var> UTC Resolved - This issue is now resolved. Provisioning times and project lifecycle operations have returned to normal. Jul <var data-var='date'> 1</var>, <var data-var='time'>18:40</var> UTC Monitoring - Provisioning times and project lifecycle operations have returned normal. We will continue to monitor. Jul <var data-var='date'> 1</var>, <var data-var='time'>17:39</var> UTC Identified - 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.

Delays in newly created project setup

Jul <var data-var='date'> 1</var>, <var data-var='time'>16:12</var> UTC Resolved - Edge Function API requests have returned to normal. This issue is now resolved. Jul <var data-var='date'> 1</var>, <var data-var='time'>15:30</var> UTC Monitoring - 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. Jul <var data-var='date'> 1</var>, <var data-var='time'>14:59</var> UTC Identified - 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. Jul <var data-var='date'> 1</var>, <var data-var='time'>14:40</var> UTC Investigating - 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.

Functions management API is returning 500s for multiple function operations

Jun <var data-var='date'>30</var>, <var data-var='time'>18:01</var> UTC Resolved - 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. Jun <var data-var='date'>30</var>, <var data-var='time'>17:06</var> UTC Monitoring - We believe the issue has resolved. We are monitoring for any recurrence. Jun <var data-var='date'>30</var>, <var data-var='time'>16:56</var> UTC Investigating - 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.

Connection issues in Supavisor us-east-1 cluster

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

Jun <var data-var='date'>26</var>, <var data-var='time'>04:00</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>26</var>, <var data-var='time'>03:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>22</var>, <var data-var='time'>14:12</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 June 26, 2026 - End time: 04:00 UTC on June 26, 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 06/26

Jun <var data-var='date'>25</var>, <var data-var='time'>18:51</var> UTC Resolved - Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved. Jun <var data-var='date'>25</var>, <var data-var='time'>18:08</var> UTC Monitoring - 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. Jun <var data-var='date'>25</var>, <var data-var='time'>17:46</var> UTC Update - 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. Jun <var data-var='date'>25</var>, <var data-var='time'>17:03</var> UTC Update - We are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems. Jun <var data-var='date'>25</var>, <var data-var='time'>16:27</var> UTC Update - We are implementing operational mitigations to try to improve upgrade performance. Jun <var data-var='date'>25</var>, <var data-var='time'>16:03</var> UTC Update - 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. Jun <var data-var='date'>25</var>, <var data-var='time'>15:32</var> UTC Update - We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades. Jun <var data-var='date'>25</var>, <var data-var='time'>15:01</var> UTC Identified - The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources. Jun <var data-var='date'>25</var>, <var data-var='time'>14:41</var> UTC Update - Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays. Jun <var data-var='date'>25</var>, <var data-var='time'>14:20</var> UTC Investigating - We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps.

Upgrade Failures

Jun <var data-var='date'>25</var>, <var data-var='time'>02:16</var> UTC Resolved - We have confirmed that the fix has been successfully applied and the issue affecting Postgres Change subscriptions has been resolved. We will continue to monitor the service, but all systems are operating normally at this time. Jun <var data-var='date'>25</var>, <var data-var='time'>00:49</var> UTC Monitoring - We have applied a fix and are monitoring the results to ensure the issue is fully resolved. Jun <var data-var='date'>24</var>, <var data-var='time'>23:58</var> UTC Identified - We have identified the cause of the elevated errors affecting Postgres change subscriptions and are actively working on a fix. We will provide another update as soon as we have additional information or progress to share. Jun <var data-var='date'>24</var>, <var data-var='time'>23:52</var> UTC Investigating - We are investigating an issue causing elevated errors for some customers using Postgres change subscriptions. Our team has identified the affected component and is actively working to determine the root cause and implement a fix. We will provide another update as soon as more information is available.

Elevated errors on Postgres change subscriptions

Jun <var data-var='date'>24</var>, <var data-var='time'>16:14</var> UTC Resolved - One of the processes in the ap-southeast-1 Supavisor cluster became overloaded, causing difficulties in starting new pools. We restarted a node to stabilize the cluster and scaled the cluster up. The issue appears resolved. Jun <var data-var='date'>24</var>, <var data-var='time'>15:59</var> UTC Investigating - We are aware of a period of degraded performance of the Shared Pooler cluster in ap-southeast-1. Affected projects experienced increased ECHECKOUTTIMEOUT errors when running queries. The window of the incident was between 14:48 to 15:25 UTC. The issue appears to be resolved. We are investigating the cause of this incident and will continue monitoring the cluster.

Degraded performance of the Shared Pooler cluster in ap-southeast-1

Jun <var data-var='date'>23</var>, <var data-var='time'>16:32</var> UTC Resolved - Project create and unpause operations have returned to normal and remained stable for the past 30 minutes. Jun <var data-var='date'>23</var>, <var data-var='time'>16:01</var> UTC Monitoring - Key updates and other mitigations have been fully deployed and project creation and unpause functionality is returning to normal. We will continue to monitor this region for stability for the next 30 minutes. Jun <var data-var='date'>23</var>, <var data-var='time'>15:46</var> UTC Update - During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect. Jun <var data-var='date'>23</var>, <var data-var='time'>15:43</var> UTC Update - Multiple mitigations have been deployed and project create performance is improving. Jun <var data-var='date'>23</var>, <var data-var='time'>15:26</var> UTC Identified - We have identified the issue is related to keys and are preparing a mitigation. Jun <var data-var='date'>23</var>, <var data-var='time'>15:16</var> UTC Investigating - We are investigating errors in creating and unpausing projects in the eu-west-1 region.

Project create and unpause errors in eu-west-1

Jun <var data-var='date'>23</var>, <var data-var='time'>14:19</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>23</var>, <var data-var='time'>13:39</var> UTC Monitoring - Latency has returned to normal levels, and we are seeing greatly improved stability across the management API. We are monitoring for any further issues. Jun <var data-var='date'>23</var>, <var data-var='time'>13:21</var> UTC Identified - We are seeing increased latency on management API requests, which results in slower-than-usual Dashboard performance, project creation and configuration changes may also be delayed. This is primarily affecting US-East-1; however, we are seeing additional latency in other regions as well. The team has identified the issue and is working on resolution.

Increased latency for Management API requests

Jun <var data-var='date'>20</var>, <var data-var='time'>00:58</var> UTC Resolved - We are not detecting any remaining network restriction list issues. Jun <var data-var='date'>20</var>, <var data-var='time'>00:48</var> UTC Update - We have now deployed a fix for this issue across all regions, and we believe this issue to be resolved. We are continuing to monitor for any remaining issues. Please contact Support if you are experiencing any problems with your network restrictions list. Jun <var data-var='date'>19</var>, <var data-var='time'>23:39</var> UTC Monitoring - We have started deploying a fix for the issue and are validating the results as the rollout progresses. We will continue to provide updates as we move toward full resolution. Jun <var data-var='date'>19</var>, <var data-var='time'>22:25</var> UTC Identified - We have identified the root cause of the issue and are actively working on implementing a fix. Jun <var data-var='date'>19</var>, <var data-var='time'>21:55</var> UTC Investigating - We are aware of some users reporting issues adding new entries to their network restriction lists, and we are currently investigating this issue.

Failed to apply network restrictions

Jun <var data-var='date'>18</var>, <var data-var='time'>10:17</var> UTC Resolved - This issue has been resolved and all previous held project updates resumed. Jun <var data-var='date'>18</var>, <var data-var='time'>08:05</var> UTC Monitoring - We have deployed a fix and are monitoring for full recovery. Project creation, pause and unpause are gradually restored within the next minutes. Jun <var data-var='date'>18</var>, <var data-var='time'>07:37</var> UTC Identified - We have identified a fix and working on recovering the impacted system. Project creation, pause and unpause functions will be restored on confirmed service recovery. Jun <var data-var='date'>18</var>, <var data-var='time'>07:09</var> UTC Update - We've identified an issue with DNS record creation returning 500 failures, preventing new project creation, pause and unpause. We have temporarily disabled new project creation while the issue is under review. Jun <var data-var='date'>18</var>, <var data-var='time'>06:39</var> UTC Investigating - We are investigating DNS Api outage impacting project creation. Impact and details are under review.

DNS record creation failures impacting project creation, restore, pause

Jun <var data-var='date'>17</var>, <var data-var='time'>17:02</var> UTC Resolved - We have now recovered all Projects affected by the outage in us-east-2. Jun <var data-var='date'>17</var>, <var data-var='time'>16:13</var> UTC Monitoring - All the identified affected projects in us-east-2 are now healthy. If your project is in us-east and not responsive, please open a ticket to let us know. Jun <var data-var='date'>17</var>, <var data-var='time'>15:44</var> UTC Identified - We have identified projects specifically impacted by this issue and are recovering affected projects. Jun <var data-var='date'>17</var>, <var data-var='time'>15:12</var> UTC Investigating - Some projects in US-East-2 are impacted by compute failures in that region. We are actively investigating the issue.

Hardware failure in us-east

Jun <var data-var='date'>17</var>, <var data-var='time'>14:10</var> UTC Resolved - All regions continue to report healthy Management API performance and platform stability. Jun <var data-var='date'>17</var>, <var data-var='time'>13:15</var> UTC Monitoring - We have resolved the degraded performance affecting our Management API in the impacted regions. All systems are now fully operational. All payment features have been re-enabled. Customers should no longer experience failed payments or failed project creations. We are continuing to monitor the system closely and will provide a final update once we have confirmed full stability. Jun <var data-var='date'>17</var>, <var data-var='time'>12:51</var> UTC Update - We are currently experiencing degraded performance with our Management API in the following regions: ca-central-1, sa-east-1, us-east-1, and us-east-2. Customers may experience failed payments, failed project creations, and degraded performance in Supabase Studio. As a precautionary measure, we have temporarily disabled the following features while we investigate: - Top up Credits - Update Billing Information - Redeem Credits To reduce impact, we have redirected traffic to healthy regions. Our team continues to actively investigate and work toward a full resolution. Jun <var data-var='date'>17</var>, <var data-var='time'>12:31</var> UTC Investigating - We are currently investigating the issue

Degraded Management API performance affecting payments and Supabase Studio

Jun <var data-var='date'>16</var>, <var data-var='time'>17:01</var> UTC Resolved - All analytics responses have returned to normal. Jun <var data-var='date'>16</var>, <var data-var='time'>16:27</var> UTC Monitoring - The mitigation has been successful and analytics endpoints are all responsive. We will continue to monitor for stability. Jun <var data-var='date'>16</var>, <var data-var='time'>16:22</var> UTC Identified - The component at issue has been identified and we are implementing mitigations. Analytics responsiveness on the impacted endpoint is begining to recover. Jun <var data-var='date'>16</var>, <var data-var='time'>16:18</var> UTC Update - We are investigating the components involved in analytics endpoints updates to isolate any changes that could have caused this problem. The issue is limited to the usage.api-requests-count endpoint. Jun <var data-var='date'>16</var>, <var data-var='time'>15:47</var> UTC Investigating - We are investigating a breakage in project usage analytics data propagation.

Project usage analytics API endpoints breakage

Jun <var data-var='date'>16</var>, <var data-var='time'>15:08</var> UTC Resolved - We have rolled out additional performance improvements to reporting API endpoints. Jun <var data-var='date'>16</var>, <var data-var='time'>13:30</var> UTC Monitoring - We are seeing things have stabilized across the fleet after further optimization work, and we are monitoring to ensure no further issues arise. Jun <var data-var='date'>16</var>, <var data-var='time'>13:01</var> UTC Identified - The mitigations rolled out have resulted in a great reduction in errors and most users should now see fully-functional logging and usage charts; however, some users may still see erroneously empty usage charts on the project home page. The team is continuing to work on this issue. Jun <var data-var='date'>16</var>, <var data-var='time'>11:26</var> UTC Monitoring - Some users are seeing errors or degraded performance on usage reportss and logs in the Supabase dashboard. The team has already rolled out mitigations and are seeing improvements. We are continuing to monitor the results.

Degraded Log Explorer in the dashboard

Jun <var data-var='date'>16</var>, <var data-var='time'>08:16</var> UTC Resolved - The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal. Jun <var data-var='date'>15</var>, <var data-var='time'>16:52</var> UTC Update - The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal. We will monitor this for continued functionality. Jun <var data-var='date'>12</var>, <var data-var='time'>11:09</var> UTC Update - Our upstream TLD provider is continuing to make changes to its network routing policies to address this issue. These changes are intended to improve regional traffic routing and reduce DNS resolution failures. We have already begun to see improvements as these changes take effect, but the issue has not yet been fully resolved. We are continuing to monitor the situation closely and work with the provider toward a complete resolution. We will provide another update as soon as more information becomes available. Jun <var data-var='date'>10</var>, <var data-var='time'>23:24</var> UTC Update - Our upstream TLD provider believes they have identified the underlying issue, and we are continuing to coordinate with them to review their findings and potential remediation options. In parallel, we are investigating other factors that may be contributing to the ongoing resolution problems affecting a subset of customers. VPNs continue to provide a workaround for impacted end users while our investigation remains ongoing. Jun <var data-var='date'> 8</var>, <var data-var='time'>17:32</var> UTC Update - We have opened a follow-up issue with our provider to address the continued problems a subset of our customers in the Americas are experiencing with top-level ".co" domain resolution. We will continue to pursue this issue until it is resolved and customers who have reported the issue are able to correctly resolve the domain name. Jun <var data-var='date'> 8</var>, <var data-var='time'>12:38</var> UTC Update - Our testing has observed that the issue is related to selected ISP resolvers to .co domains. The clients impacted are mainly located in us-east-1, us-east-2 region. We continue to review this issue for resolution with our third party network partner. Jun <var data-var='date'> 8</var>, <var data-var='time'>06:37</var> UTC Monitoring - The third-party has confirmed a fix has been implemented and we are validating the results with our impacted users. Jun <var data-var='date'> 8</var>, <var data-var='time'>03:39</var> UTC Identified - We are investigating reports of DNS resolution failures affecting a subset of customers connecting to Supabase project endpoints. This appears to be related to a third-party issue with .co TLD resolution impacting multiple DNS providers. Customers may be able to bypass this issue by using a VPN while we work towards resolution. We will update the statuspage when we have more information to share.

DNS Resolution Failures for TLD .co users

Jun <var data-var='date'>16</var>, <var data-var='time'>08:15</var> UTC Resolved - The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal. Jun <var data-var='date'>15</var>, <var data-var='time'>16:52</var> UTC Update - The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal. We will monitor this for continued functionality. Jun <var data-var='date'>12</var>, <var data-var='time'>14:42</var> UTC Monitoring - We continue to work with the relevant provider and have seen improvements. We are monitoring the progress that has been made to ensure it continues. Jun <var data-var='date'> 9</var>, <var data-var='time'>13:26</var> UTC Update - We are engaged with senior networking team members at the impacted provider. They are actively investigating the domain name resolution issues we have reported. If you are continuing to experience .co name resolution issues in Brazil, please update your ticket or open a new ticket to let us know so we can add that information to the investigation. Jun <var data-var='date'> 3</var>, <var data-var='time'>21:32</var> UTC Update - We continue to work with the service provider to resolve the residual access issues. We have scheduled direct consultations with the provider to attempt to resolve the issue. May <var data-var='date'>19</var>, <var data-var='time'>22:30</var> UTC Update - We are continuing to contact the ISP in Brazil to work through this issue: however they have remained unresponsive to outreach. We are exploring other options to get in touch with them. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share. May <var data-var='date'>14</var>, <var data-var='time'>22:23</var> UTC Identified - We are continuing to contact the ISP in Brazil to work through this issue. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share. May <var data-var='date'>14</var>, <var data-var='time'>16:37</var> UTC Update - We have made contact with the ISP in Brazil and are working through their support process for this issue. Customers may be able to bypass the problem by using a VPN or alternative network while we work towards resolution. May <var data-var='date'>14</var>, <var data-var='time'>15:54</var> UTC Update - We have isolated the issue to a specific Internet provider in Brazil and are working to contact that provider to resolve the issue. We will update the statuspage when we have more information to share. May <var data-var='date'>14</var>, <var data-var='time'>15:34</var> UTC Investigating - We are investigating reports of some access issues to Supabase IP addresses from a network provider in Brazil.

Access Issues From Some Providers in Brazil

Jun <var data-var='date'>13</var>, <var data-var='time'>00:40</var> UTC Resolved - All residual jobs have drained. Storage performance and job activity is normal. Jun <var data-var='date'>12</var>, <var data-var='time'>23:57</var> UTC Update - Job queues continue to drain. We will actively monitor until they are complete. Jun <var data-var='date'>12</var>, <var data-var='time'>20:26</var> UTC Monitoring - Backlog is being effectively processed and operations have returned to normal. We continue to monitor the performance in us-west-2. Jun <var data-var='date'>12</var>, <var data-var='time'>19:30</var> UTC Update - We are seeing improvement in the performance of us-west-2 after implementation of our mitigation strategies. Storage operation is returning to normal. We will continue to monitor performance in this region. Jun <var data-var='date'>12</var>, <var data-var='time'>18:28</var> UTC Update - We have implemented further mitigations and are tracking their progress. We continue to actively work this issue. Jun <var data-var='date'>12</var>, <var data-var='time'>17:29</var> UTC Update - The team is still working on a solution, and mitigation work is underway. Jun <var data-var='date'>12</var>, <var data-var='time'>16:30</var> UTC Update - We are implementing load mitigation strategies to improve the performance of storage requests in US-West-2. Jun <var data-var='date'>12</var>, <var data-var='time'>16:00</var> UTC Identified - Users in US-West-2 are seeing increased latency on storage requests. The team has identified the issue and is working on a solution.

Storage users in US-West-2 experiencing increased latency on storage requests

Jun <var data-var='date'>10</var>, <var data-var='time'>00:00</var> UTC Resolved - From 00:52 to 01:02 UTC on 10th June an internal deployment in one of the ap-northeast-1 and ap-northeast-2 clusters caused a higher connection failure rate. Users would have experienced failing connections, increased query latency and would not have been able to retrieve pooler metrics. The deployment has now been reverted and full service availability restored.

Is Supabase down?

Supabase status is UP

Lastest published events

Endpoints in Americas regions returning 500 Internal server error

Degraded project creation success rates in the ca-central-1 region

Errors when attempting to view advisor results in the Supabase dashboard

Supabase Services, Components and Regions

Recent Supabase events

Scheduled Platform Maintenance July 14th, 2026

Endpoints in Americas regions returning 500 Internal server error

Degraded project creation success rates in the ca-central-1 region

Errors when attempting to view advisor results in the Supabase dashboard

Issues with Restore to New Project

Delays in newly created project setup

Get your FREE account now,
5 monitors included!

Is Supabase down?

Supabase status is UP

Lastest published events

Endpoints in Americas regions returning 500 Internal server error

Degraded project creation success rates in the ca-central-1 region

Errors when attempting to view advisor results in the Supabase dashboard

Supabase Services, Components and Regions

Recent Supabase events

Scheduled Platform Maintenance July 14th, 2026

Endpoints in Americas regions returning 500 Internal server error

Degraded project creation success rates in the ca-central-1 region

Errors when attempting to view advisor results in the Supabase dashboard

Issues with Restore to New Project

Delays in newly created project setup

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!