Supabase Outage History
Past incidents and downtime events
Complete history of Supabase outages, incidents, and service disruptions. Showing 50 most recent incidents.
July 2026(9 incidents)
Degraded log ingestion
7 updates
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.
Elevated JWT authorization errors
4 updates
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 delays in AP regions
7 updates
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.
Endpoints in Americas regions returning 500 Internal server error
6 updates
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.
Degraded project creation success rates in the ca-central-1 region
6 updates
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.
Errors when attempting to view advisor results in the Supabase dashboard
4 updates
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.
Issues with Restore to New Project
2 updates
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.
Delays in newly created project setup
3 updates
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.
Functions management API is returning 500s for multiple function operations
4 updates
Edge Function API requests have returned to normal. This issue is now resolved.
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.
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 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.
June 2026(17 incidents)
Connection issues in Supavisor us-east-1 cluster
3 updates
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 believe the issue has resolved. We are monitoring for any recurrence.
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.
Project status change failures in multiple regions
26 updates
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.
Upgrade Failures
10 updates
Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved.
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.
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 are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems.
We are implementing operational mitigations to try to improve upgrade performance.
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 aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades.
The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources.
Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays.
We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps.
Elevated errors on Postgres change subscriptions
4 updates
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 have applied a fix and are monitoring the results to ensure the issue is fully resolved.
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 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.
Degraded performance of the Shared Pooler cluster in ap-southeast-1
2 updates
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 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.
Project create and unpause errors in eu-west-1
6 updates
Project create and unpause operations have returned to normal and remained stable for the past 30 minutes.
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.
During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect.
Multiple mitigations have been deployed and project create performance is improving.
We have identified the issue is related to keys and are preparing a mitigation.
We are investigating errors in creating and unpausing projects in the eu-west-1 region.
Increased latency for Management API requests
3 updates
This incident has been resolved.
Latency has returned to normal levels, and we are seeing greatly improved stability across the management API. We are monitoring for any further issues.
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.
Failed to apply network restrictions
5 updates
We are not detecting any remaining network restriction list issues.
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 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 identified the root cause of the issue and are actively working on implementing a fix.
We are aware of some users reporting issues adding new entries to their network restriction lists, and we are currently investigating this issue.
DNS record creation failures impacting project creation, restore, pause
5 updates
This issue has been resolved and all previous held project updates resumed.
We have deployed a fix and are monitoring for full recovery. Project creation, pause and unpause are gradually restored within the next minutes.
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'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 are investigating DNS Api outage impacting project creation. Impact and details are under review.
Hardware failure in us-east
4 updates
We have now recovered all Projects affected by the outage in us-east-2.
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 identified projects specifically impacted by this issue and are recovering affected projects.
Some projects in US-East-2 are impacted by compute failures in that region. We are actively investigating the issue.
Degraded Management API performance affecting payments and Supabase Studio
4 updates
All regions continue to report healthy Management API performance and platform stability.
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.
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 are currently investigating the issue
Project usage analytics API endpoints breakage
5 updates
All analytics responses have returned to normal.
The mitigation has been successful and analytics endpoints are all responsive. We will continue to monitor for stability.
The component at issue has been identified and we are implementing mitigations. Analytics responsiveness on the impacted endpoint is begining to recover.
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.
We are investigating a breakage in project usage analytics data propagation.
Degraded Log Explorer in the dashboard
4 updates
We have rolled out additional performance improvements to reporting API endpoints.
We are seeing things have stabilized across the fleet after further optimization work, and we are monitoring to ensure no further issues arise.
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.
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.
DNS Resolution Failures for TLD .co users
8 updates
The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.
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.
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.
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.
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.
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.
The third-party has confirmed a fix has been implemented and we are validating the results with our impacted users.
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.
Storage users in US-West-2 experiencing increased latency on storage requests
8 updates
All residual jobs have drained. Storage performance and job activity is normal.
Job queues continue to drain. We will actively monitor until they are complete.
Backlog is being effectively processed and operations have returned to normal. We continue to monitor the performance in us-west-2.
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.
We have implemented further mitigations and are tracking their progress. We continue to actively work this issue.
The team is still working on a solution, and mitigation work is underway.
We are implementing load mitigation strategies to improve the performance of storage requests in US-West-2.
Users in US-West-2 are seeing increased latency on storage requests. The team has identified the issue and is working on a solution.
Higher connection failure rate for ap-northeast-1 and ap-northeast-2
1 update
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.
Errors impacting pause, restore, and backup operations in us-east-2 (Ohio)
4 updates
All operations have continued as normal since moving this incident to Monitoring. We are resolving this incident.
The redeployment has returned pause, restore and backup operations in the affected region to normal. We will continue to monitor for any residual impact.
We have identified the cause is related to a recent deployment. We have initiated a redeploy to address the issue.
We are currently investigating an issue affecting pause, restore, and backup operations for projects in us-east-2 (Ohio) We will provide further updates as more information becomes available.
May 2026(12 incidents)
Access Issues From Some Providers in Brazil
10 updates
The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.
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.
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.
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.
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.
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.
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.
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.
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.
We are investigating reports of some access issues to Supabase IP addresses from a network provider in Brazil.
Branch creation degradation
4 updates
Branch creation continues to be stable.
Branch creation has returned to normal. We are investigating a set of factors that likely contributed to the degradation, including cluster load, lock contention, and service start-up sequencing to identify areas for improvement going forward. We will monitor our platform for another 30 minutes to ensure the problem has fully resolved before resolving the incident.
We continue investigating different possible underlying causes and will provide updates as progress is made.
We are seeing degradation in branch creation linked to database migration locks. We are investigating and will share further updates as progress is made.
Login issues for SSO and Email accounts on Supabase Dashboard
6 updates
The issue affecting SSO logins has now been resolved. Thank you for your patience while we worked through this issue.
We have applied a fix and are seeing login services return to normal. We will continue to monitor authentication success rates over the next 60 minutes to ensure stability.
A fix has been implemented and is currently being rolled out. We will continue to provide updates as the deployment progresses.
We have identified the issue as being related to a recent key rotation and are currently working on a fix.
We are currently investigating an issue causing login failures for some users attempting to authenticate to the Supabase dashboard via SSO or email/password login flows. Affected users may see an error similar to: “captcha protection: request disallowed (sitekey-secret-mismatch)” Currently logged-in users are not affected, and GitHub authentication continues to operate normally. We will continue to provide updates as more information becomes available.
Users that are already logged in are not affected.
Network restrictions preventing read replica communication
8 updates
Communication between read replicas and their primaries for impacted projects has been restored. This incident is now resolved.
We have merged the fix and are monitoring for stability.
We have developed a fix and it is currently being validated. We will provide more updates soon.
Our team continues to work on implementing a fix for the issue. We will provide additional updates as progress is made.
Our team continues to work on implementing a fix for the issue. We are continuing to monitor the impact and will provide additional updates as progress is made.
We have identified the cause of the issue impacting read replica communication for projects. Our team is actively working on a fix and continuing to assess the impact to affected projects.
We are reviewing the impact of this issue, which is limited to projects with read replicas and network restrictions. We continue to both investigate mitigation options for the issue and identify projects that may be impacted.
Network restrictions are preventing read replicas from communicating with their primaries for a limited number of customer projects. We are actively investigating this issue.
Paused Projects Showing Incorrect Resume Deadline
5 updates
The UI message incident has been resolved.
This change has been reverted. We are monitoring to ensure things remain stable.
The revert of the change is in process.
We’ve isolated the cause of the issue to a recent change and are working on reverting it now.
We are currently investigating a UI issue affecting paused projects, where an incorrect resume deadline is displayed in the dashboard. The message incorrectly states that projects can be resumed within 90 days while also displaying today’s date as the expiry date. For example: “All data, including backups and storage objects, remains safe. You can resume this project from the dashboard within 90 days (until 20 May 2026). After that, this project will not be resumable, but data will still be available for download.” Please note this is a display issue only. Projects paused within the last 90 days can still be resumed successfully. All project data, including backups and storage objects, remains safe and unaffected.
Log ingestion issues
3 updates
This incident has been resolved, and log delivery has returned to normal. During the incident, some logs may have been delayed or unavailable. While some upstream sources may retry delivery automatically, we cannot guarantee recovery of all missing logs from the affected period. Thank you for your patience while we worked to resolve this.
Logging systems have returned to normal operation. During the incident, some logs may have been delayed or unavailable. While certain upstream log sources may retry delivery automatically, we cannot guarantee recovery of all missing logs generated during the affected time period. We will continue monitoring closely to ensure ongoing stability.
Customers may experience delayed log ingestion or periods where logs are unavailable. We will provide updates while we work to resolve the issue.
Auth Service Update
3 updates
All changes hav been applied.
The update has been implemented. Service changes can be made. We will monitor the effect for the next 30 minutes to ensure stability.
We need to implement a time-sensitive update to our Auth service. Please do not make any changes to your Auth service until we have completed this update.
Edge Traffic Issues
5 updates
We've determined that the connectivity issues are isolated to users accessing Supabase through Mullvad VPN and potentially other VPN providers. The root cause appears to be network disruptions involving a specific colocation/transit provider used by Mullvad, rather than an issue with Supabase or Cloudflare infrastructure. We've reached out to Mullvad support, but as this is dependent on external providers, there are no further mitigation steps we can take internally. Users experiencing issues are advised to avoid affected VPN networks or contact their VPN provider directly for support. The incident is now resolved
Our investigation has identified traffic loss along a specific network path associated with a VPN exit point located in Western Europe. Some customers are experiencing connectivity issues that impact a subset of users connecting through certain VPN providers, including Mullvad. Customers impacted while using Mullvad can contact Mullvad support directly to help raise visibility into the issue from their side.
We are continuing to actively investigate the connectivity issues impacting access to Supabase APIs for some users. Our team remains engaged in identifying the underlying cause and validating the scope of impact. We will continue to provide updates as our investigation progresses.
We are continuing to investigate connectivity issues impacting access to Supabase APIs, which may result in connection timeout errors or rejected connections for some users. At this time, we have narrowed the issue down to traffic originating from at least one VPN provider (Mullvad VPN). However, we cannot yet confirm whether additional VPN providers may also be impacted. We are actively working to identify the root cause and will continue to provide updates as we learn more.
We've observed traffic from upstream providers of a VPN provider is no longer reaching our servers. We're investigating the cause and will keep you updated.
Error spikes in one of the eu-central-1 Supavisor clusters
1 update
Between 15:25 and 15:33 and between 15:38 and 15:41 we observed error spikes in one of the eu-central-1 Supavisor clusters. Users reported failures in connecting to postgres via Supavisor Errors reported: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode
Network connectivity in us-east-1-az4
17 updates
Recovery efforts are completed and this incident is now resolved. Thank you for your patience throughout this incident.
Our infrastructure provider has resolved the underlying incident, and impacted services have recovered. We have completed recovery efforts for affected projects, re-enabled project creation, pausing, and compute resizes in the us-east-1 region, and are now monitoring the platform to ensure continued stability.
Our infrastructure provider has resolved the underlying incident, and the majority of impacted projects have now recovered. Our team is currently working through the remaining projects that did not automatically self-heal during recovery and is actively restoring them manually where needed. We have also re-enabled project creation, pausing, and compute resizes in the us-east-1 region. We are continuing to monitor platform stability closely and will provide additional updates as recovery progresses.
Our team continues to make progress restoring impacted projects safely and as quickly as possible. To support recovery efforts, project pausing and new project creation in the us-east-1-a4 region continue to be disabled. While recovery efforts are moving forward, full resolution is still expected to take several more hours based on the latest guidance from our infrastructure provider. We understand the impact this is having and appreciate your continued patience. We’ll continue to share updates as more information becomes available.
Our team continues to make progress restoring impacted projects safely and as quickly as possible. To support recovery efforts, project pausing and new project creation in the us-east-1-a4 region continue to be disabled. While recovery efforts are moving forward, full resolution is still expected to take several more hours based on the latest guidance from our infrastructure provider. We understand the impact this is having and appreciate your continued patience. We’ll continue to share updates as more information becomes available.
Our team is actively working to bring impacted projects back online as quickly and safely as possible. While we are seeing progress, full recovery may still take several hours based on the latest guidance from our infrastructure provider. We appreciate your patience and will continue to share updates as more information becomes available.
Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
We're starting to see a number of affected projects starting to recover. We're still working with our upstream providers on a full recovery of all affected projects.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We've disabled pausing projects in us-east-1. We recommend not changing project configurations at this time. Users cannot access their databases or run any authentication-dependent services. We are continuing to monitor this situation with our upstream provider.
We have disabled project creation in us-east-1. We will provide another update in an hour, if not sooner.
We are waiting on a resolution from our upstream provider. We will provide an update in an hour.
We have identified the root cause of the connection issues as an outage with an upstream provider affecting a single availability zone (us-east-1a). All affected projects are located in this zone.
Increased connection times for Supavisor since about 00:10 UTC is affecting a limited number of projects in us-east-1
Customer Projects Experiencing Upgrade Issues
5 updates
Upgrade operations have returned to normal.
We have identified the root cause and developed a fix, which has been applied in production. Projects which have failed to upgrade will be automatically recovered and returned to ACTIVE_HEALTHY without manual intervention. Any future upgrades should complete successfully. We are continuing to monitor recovery and system stability closely.
We are continuing to investigate issues impacting project upgrades. We have observed that the majority of affected projects are successfully returning to a healthy state on their previous PostgreSQL version following failed upgrade attempts. Our engineering team is actively working to manually restore the remaining projects that are still stuck during the upgrade process. As a precaution, we recommend that customers do not attempt to upgrade their projects until this incident has been fully resolved. We will continue to provide updates as information becomes available.
We are continuing to work on a fix for this issue.
Our engineering team are investigating issues with customer projects being stuck when upgrading Postgres version. We advise that you do not upgrade your project until the incident is resolved.
Supavisor connectivity in eu-central-1
1 update
From 15:30 to 7:00 UTC, for projects in eu-central-1, a Supavisor node experienced connectivity issues and was not able to connect to customer databases, causing checkout timeouts and auth query failed errors. This has been resolved and Supavisor is fully available.
April 2026(12 incidents)
403 errors for PostgREST requests
6 updates
This is now resolved. Thank you for your patience while we worked to resolve this issue.
The exceptions fix has been rolled out, and we are monitoring for continued stability.
We are continuing to work on a fix. We’ll share further updates as progress is made.
We are continuing to work on a fix for this issue.
The issue has been identified and we are working on a fix.
We are investigating 403 errors for PostgREST requests across multiple regions.
Some Projects Unreachable following Project Restart
8 updates
All projects are patched and this is now resolved. Thank you for your patience while we ensured all projects were updated.
The fix has been rolled out, and we are monitoring for continued stability. Any remaining impacted projects are being manually patched.
The permanent fix has now been rolled out across the fleet. We are continuing to manually patch any remaining impacted projects to restore service.
We’ve identified additional impacted projects and are currently working to manually patch and restore them. We are also continuing to roll out a fix across the fleet to prevent further impact.
All impacted projects with open support tickets have now been manually patched and restored. We are currently rolling out a fix across the fleet to prevent further impact. We will continue to monitor progress and provide updates.
Our team is actively working on a fix and is manually patching impacted projects to restore service as quickly as possible. If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved.
We’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script. This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully. This can result in projects remaining offline. We are working on a fix to restore service. If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved.
We’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script. This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully. This can result in projects remaining offline. We are working on a fix to restore service.
Some projects unavailable across multiple regions
7 updates
This incident has been resolved.
We believe all users affected by this particular issue have been resolved. The team is going to keep an eye on these error rates to ensure we catch any that didn't originally appear, or that no new issues arise. We appreciate your patience as we worked through this issue.
The team is continuing their mitigation efforts. We've fixed and restarted most of the affected projects. We're continuously looking for any others that are affected so we can be sure to get them all fixed.
The team is still working to bring these back online, and have a fix under way. Many users can also resolve this on their own via a project restart. This can be performed from the dashboard for your own projects at any time. But for those who are still seeing issues after a restart, we will be pushing a fix soon.
We have identified this issue across multiple regions, not just eu-west-3 as originally suspected. We are expanding the scope of efforts to bring affected projects back online. Users can also resolve this, in most cases, on their own via a project restart. This can be performed from the dashboard for your own projects at any time.
The team is continuing to work through affected projects; however, a project restart is also effective. This can be performed from the dashboard for your own projects at any time.
We are seeing an increase in projects unavailable in eu-west-3 following an upstream issue with EC2 instances in the region. The team is working on restoring access to these projects
Inadvertently disabled pg_graphql for some projects
1 update
A modification to existing projects was deployed due to the recently communicated Data API and pg_graphql changes. https://github.com/orgs/supabase/discussions/45329 This modification was supposed to disable pg_graphql for projects that had not seen usage in the last 30 days. Due to a misconfiguration, this targeted more projects than intended. We are deeply sorry for the inconvenience and have since addressed the issue. For those using pg_graphql actively, you may have seen pg_graphql extension is not enabled in the logs for your project and you can safely re-enable this. If you have been impacted, or you are unable to re-enable pg_graphql, please contact success@supabase.io
Increased errors in project creation and configuration changes in US-East-2 and AP-Northeast-1
5 updates
This issue has now been resolved and projects have returned to normal.
Projects have recovered and capacity has been restored. All previously affected regions have been re-enabled, and we will continue to monitor to ensure stability.
Capacity has been freed, and the regions have been re-enabled. The team is currently working on resolving any failed project starts, resizes, restarts, or other configuration changes during this event.
US-East-2 and AP-Northeast-1 have been disabled for project creation and configuration change actions, and the team is currently working to free additional capacity in these regions.
We are seeing new project creation, resize requests, and project restart failures due to capacity issues in us-east-1. We are disabling project creation, project resize actions, and project restarts in these regions. We have already reached out to our provider for additional capacity, and will update here as we have additional information.
Newly created projects may be unreachable
4 updates
The issue has been resolved and DNS resolution is now operating normally.
A fix has been implemented, and we are seeing improvements in DNS resolution. We’re closely monitoring to ensure the issue is fully resolved and services remain stable.
We are currently experiencing an issue propagating new DNS records for our zone. We are working closely with our upstream network providers technical team to implement a fix and will share updates as we learn more.
We are currently investigating reports that newly created projects may be unreachable. Initial findings indicate DNS resolution failures. We will provide an update as soon as more information is available.
Edge Functions: Several users reported 503 errors with SUPABASE_EDGE_RUNTIME_ERROR error code
1 update
Incident Summary A health check designed to prevent Out-of-Memory (OOM) conditions began closing some incoming connections, which led to 503 errors for a subset of users. These errors were initially surfaced under a generic SUPABASE_EDGE_RUNTIME_ERROR code. Timeline & Actions Sunday, 26: Issue detected as user reports of 503 errors increased. Investigation into root cause began. Monday, 27: Introduced a more accurate error code (SUPABASE_EDGE_RUNTIME_SERVICE_DEGRADED) and implemented infrastructure changes to mitigate impact. Tuesday, 28: Adjusted conditions for returning 503 responses to be less aggressive. Prepared a “retry-on-degraded” mechanism (not yet deployed). Current Status Mitigations are in place and improvements to error handling are ongoing. Further resilience enhancements will be deployed shortly.
Increased Errors on HTTP Endpoints
18 updates
All metrics have been nominal and stable for several hours now, and our upstream provider has resolved their incident.
We've received confirmation from our networking provider that there is recovery across all regions. We are able to corroborate this with our own metrics collections. We will continue to monitor for a bit, but we believe this to be resolved at this time. We apologize for the trouble, and we appreciate your patience.
We've seen a marked improvement in error rates across all regions in the last few minutes. We are still waiting on confirmation from our provider on status, but we believe things to be improved at the moment. We'll keep working on this until we have for sure reached a resolution.
We recognize that some of our users, especially in parts of North and South America, are continuing to experience DNS and 5XX errors when trying to connect to their projects. We have escalated this issue with our network provider and will work with them continuously until the problems are resolved.
Some users continue to experience errors. We are raising the issue with our provider.
Our upstream provider has reported their incident resolved. We will continue to monitor for any errors our customers may be experiencing for another 30 minutes.
The fix that our upstream provider implemented has taken effect. Service has significantly improved across all previously impacted regions. There are still residual elevated error rates in a handful of regions and we will continue to work with our provider to eliminate them.
Our upstream provider has rolled the fix out to most regions. While we are seeing improvement, we are still seeing increased error rates in Mexico and Brazil and are continuing to work with them until this is fully resolved.
Upstream provider mitigations are still under way, and we are seeing improvements incrementally as routing regions have the mitigations applied. We are still seeing particular impact in South America, but some users in North America may still be affected as well. We anticipate continued incremental improvements and will update as we get more information.
Our upstream networking provider has identified a fix and is currently implementing a fix. We are seeing preliminary improvements to error rates for users in North America, but are still following this issue closely with our provider.
Our upstream networking partner is continuing their investigation. We will continue to post regular updates as we have more information.
Our upstream networking provider has discovered an issue and has declared an incident on their side. They are currently working toward resolution. We are actively working with them and will provide updates on progress as more information is available.
We continue to have active lines of investigation going with our upstream network provider partners, and are still working toward a resolution. This issue affects the network-level access to projects. The projects themselves and the data in them are safe and unaffected. Users are seeing two separate symptoms of these networking issues: 1. DNS Lookup failures for supabase project URLs 2. 530 responses to HTTP requests to supabase project API Endpoints
We continue to work with partners and investigate.
We have further clarified the scope and impact of the issues currently affecting users. A subset of users across North and South America are experiencing DNS resolution failures and HTTP 530 errors. These symptoms indicate a networking-related issue impacting the availability of Supabase projects. We are actively working with both internal teams and external network providers to isolate the root cause and determine the most effective path to resolution. We will continue to provide updates as more information becomes available.
We are actively investigating this issue and working with relevant partner organizations. At this time, we do not believe this issue is specific to any particular network provider. A subset of users continue to be impacted in both South and North America.
We are currently investigating reports of users experiencing login issues when using Supabase Auth. At this time, the impact appears to be limited to a subset of users, primarily in North and South America. The exact cause and scope are still being determined. Our team is actively working to identify the root of the issue and will provide updates as more information becomes available. We appreciate your patience while we investigate.
We are currently investigating reports of users experiencing login issues when using Supabase Auth. At this time, the impact appears to be limited to a subset of users, primarily in South America. The exact cause and scope are still being determined. Our team is actively working to identify the root of the issue and will provide updates as more information becomes available. We appreciate your patience while we investigate.
Transactional Email Delivery Delays
4 updates
Email queues have returned to normal.
Customers will continue to see these delayed transactional emails while we clear the backlog. We will provide another update once these queued emails are sent.
We have made progress investigating the specific causes of the email spike and are determining appropriate next steps to improve clearance of the backlog.
We are experiencing delays in delivery of some of our email to customers related to transactions, including new welcome, oauth-approved, project-shutdown, and payment-failure notifications. This has caused some customers to receive notifications after their issue has been resolved (for example, payment failure notifications after payment has been issued). We are actively monitoring the email delivery queue and expect the delays to be eliminated over time. We will update this status as appropriate.
Project creation failures in some APAC regions
3 updates
Capacity has been fully restored in the impacted APAC regions, and project creation is operating normally.
We are recovering capacity in the impacted APAC regions and are seeing improvements in project creation success rates. We will continue to monitor to ensure stability.
We are currently investigating an issue affecting project creation in some APAC regions. Users may experience failures when attempting to create new projects in impacted regions. Existing projects are not impacted. Our team is actively working to mitigate the issue and restore normal availability. We will share further updates as more information becomes available.
Logs currently inaccessible via the Dashboard and Log Drains
4 updates
This incident has been resolved.
All log sources have been restored and logs should be available to users again now. We are keeping an eye on things to ensure ongoing stability.
The underlying logging platform has stabilized, and some log sources have been restored and are successfully ingesting logs. The team is working to restore the rest of the log sources now.
Users may see errors when attempting to retrieve logs via the Supabase dashboard or may not see new logs arriving via log drains. The team has identified the issue and is working on a fix. Underlying projects are unaffected, this is only affecting the logging service.
Increased error rates for plan upgrades
4 updates
The issue causing increased error rates during plan upgrades has been resolved. All systems are operating normally.
A fix has been applied, and we are monitoring to ensure stability.
We have identified the cause of increased error rates affecting plan upgrades and are working on a fix. We will provide further updates as progress is made.
We are currently investigating increased error rates affecting plan upgrades. Our team is actively working to identify the root cause and restore normal functionality. We will provide updates as more information becomes available.
📡 Tired of checking Supabase status manually?
Better Stack monitors uptime every 30 seconds and alerts you instantly when Supabase goes down.