Störungsverlauf von Supabase

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

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 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'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 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.

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 are aware of reports of elevated legacy JWT authorization errors on edge functions in some regions

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.

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

Edge function operations are normal.

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.

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

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

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

Project creation is recovering. We are actively tracking recovery.

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 has returned to normal. The issue is now resolved.

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

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

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

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

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.

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

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.

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

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 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 have restored project creation startup time in ca-central-1 and are monitoring the situation for full recovery.

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

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 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've deployed the fix and are now monitoring the issue.

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

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.

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

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

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.

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

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.

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.

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.

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

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.

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

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.

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

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

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.

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 are continuing to work on a fix for the issue and will provide updates 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.

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 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 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 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 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 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 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 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 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 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.

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'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.

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 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.

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.

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.

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.

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.

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 are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps.

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

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

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

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.

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

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

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.

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.

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

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.

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.

We have applied a fix and are monitoring the results to ensure the issue is fully 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.

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.

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.

We are investigating errors in creating and unpausing projects in the eu-west-1 region.

We have identified the issue is related to keys and are preparing a mitigation.

Multiple mitigations have been deployed and project create performance is improving.

During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect.

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.

Project create and unpause operations have returned to normal and remained stable for the past 30 minutes.

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.

Latency has returned to normal levels, and we are seeing greatly improved stability across the management API. We are monitoring for any further issues.

This incident has been resolved.

We are aware of some users reporting issues adding new entries to their network restriction lists, and we are currently investigating this issue.

We have identified the root cause of the issue and are actively working on implementing a fix.

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.

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.

We are not detecting any remaining network restriction list issues.

We are investigating DNS Api outage impacting project creation. Impact and details are under review.

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.

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.

We have deployed a fix and are monitoring for full recovery. Project creation, pause and unpause are gradually restored within the next minutes.

This issue has been resolved and all previous held project updates resumed.

Some projects in US-East-2 are impacted by compute failures in that region. We are actively investigating the issue.

We have identified projects specifically impacted by this issue and are recovering affected projects.

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.

We have now recovered all Projects affected by the outage in us-east-2.

We are currently investigating the issue

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.

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.

All regions continue to report healthy Management API performance and platform stability.