Supabase

Project lifecycle operations are behaving normally.

Project lifecycle operations have remained stable. We will continue to monitor the platform.

We are observing recovery in project lifecycle operations. Our team is investigating the root cause and actively working to prevent recurrence.

We are experiencing degradation of project lifecycle activities. We are investigating.

This incident has been resolved.

The fix has been rolled out to us-east-1. We will continue to monitor both regions for stability.

The fix has been implemented for ap-northeast-2 and we're working on implementing the fix for us-east-1. We will continue to provide updates as progress is made.

We are continuing to work on a fix and will provide updates as things progress.

Projects running Postgres version 14 in us-east-1 and ap-northeast-2 may experience query slowness. We've identified the cause and are working on a fix.

This incident has been resolved.

Error rates have returned to normal, and the service is operating as expected. The team continues to investigate the underlying cause of the latency and spike in 503 errors.

We are investigating reports of increased Edge Function latency and elevated rates of HTTP 503 responses, beginning at approximately 06:00 UTC. Our team is working to identify the cause and will provide further updates as they become available.

This incident has been resolved.

We implemented a fix and are monitoring the system.

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

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

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

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

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

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

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

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

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

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

This incident has been resolved.

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

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

We have rolled out a version of the fix across all regions that will prevent recurrence of the issue. Users still affected by project outages are encouraged to restart their projects.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Project creation has returned to baseline consistently.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

This incident has been resolved.

We have identified a degraded Supavisor node and we have rolled out a fix. We are monitoring to ensure continued stability. Confirmed Impact: On Aug 24, 2026 between 14:30 and 15:20 UTC we observed increased rates of connection timeouts connecting to Supavisor in us-east-1 due to a degraded node.

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

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

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

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

We are continuing to rollout the fix to further regions.

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

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

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

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

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

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

The issue has been resolved.

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

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

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

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

This incident has been resolved.

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

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

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

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

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

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

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

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

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

This incident has been resolved.

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

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.

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.

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

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.

UPDATE: We are currently pushing a fix to address the root cause. We'll provide another update once the fix has been fully deployed.

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

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.

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

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

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

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

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

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

We are developing a fix for the upgrade issues.

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

We are continuing to investigate project upgrade issues.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

We are continuing to investigate this issue.

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

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

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

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

The incident has been resolved.

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

We have identified that the issue is with an upstream DNS provider, causing DNS creation delays for newly created, unpaused, or updated databases. Our team is actively monitoring the situation and will provide further updates as more information becomes available.

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

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

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

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

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

We are continuing to investigate the issue.

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

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

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

We have identified the cause of the issue and are working to restore normal log ingestion. Customers may continue to experience delays in new logs appearing.

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

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

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

We have identified the cause of the SSO login failures affecting the us-east-1 region and are working to implement a fix. We will continue to provide updates as progress is made.

We are investigating an issue causing SSO login failures in the us-east-1 region. Our team is actively investigating the cause and will provide updates as more information becomes available.

Documentation search functionality has been restored.

We noticed the search function for our documentation was not available as it should be. We're making the necessary updates to fix that problem.

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

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

We have identified and mitigated the issue that was blocking DNS updates. DNS record creation is succeeding, and latency has returned to normal levels. A subset of projects that encountered provisioning failures during the incident will require DNS records to be backfilled, and we are actively remediating these affected projects.

We have identified the cause of delays in DNS records creation and are actively working on a fix. We will continue to provide updates as things progress.

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

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

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

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

We are continuing to investigate this issue.

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

Authentication operations have returned to normal consistently.

Authentication has returned to normal.

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

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

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.

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

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

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

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

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

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

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.

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

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

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.

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.

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

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.

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

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

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.

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.

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.

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.

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.

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

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.

This issue has been resolved.

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.

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

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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

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

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.

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.

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.

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.

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.

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.

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

Edge function operations are normal.

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

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.

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

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

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

Project creation is recovering. We are actively tracking recovery.

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

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

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

We are aware of project creation taking longer than normal in AP regions. A retry should enable completion of creation for those impacted. NOTE: This incident is not related to the ongoing capacity issues incident we are monitoring.

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

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.

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

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

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

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

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

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

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.

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.

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

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.

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

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

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.

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.

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

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.

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

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

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.