Supabase Outage History
Supabase is up right nowPingoru has recorded 186 incidents for Supabase: 186 in the last 12 months and 83 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 13 | 51 of 720 (7%) |
| May 2026 | 13 | 369 of 744 (50%) |
| June 2026 | 17 | 243 of 720 (34%) |
| July 2026 | 25 | 353 of 744 (47%) |
| August 2026 | 22 | 547 of 744 (74%) |
| September 2026 | 36 | 148 of 720 (21%) |
| October 2026 | 16 | 268 of 582 (46%) |
Incidents, newest first
Minor June 24, 2026 Elevated errors on Postgres change subscriptions 2h 23m Realtime
Started Jun 24, 2026, 11:52 PM UTC· resolved Jun 25, 2026, 02:16 AM UTC
- investigating Jun 24, 2026, 11:52 PM UTC
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.
- identified Jun 24, 2026, 11:58 PM UTC
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.
- monitoring Jun 25, 2026, 12:49 AM UTC
We have applied a fix and are monitoring the results to ensure the issue is fully resolved.
- resolved Jun 25, 2026, 02:16 AM UTC
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.
Minor June 24, 2026 Degraded performance of the Shared Pooler cluster in ap-southeast-1 14m
Started Jun 24, 2026, 03:59 PM UTC· resolved Jun 24, 2026, 04:14 PM UTC
- investigating Jun 24, 2026, 03:59 PM UTC
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.
- resolved Jun 24, 2026, 04:14 PM UTC
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.
Minor June 23, 2026 Project create and unpause errors in eu-west-1 1h 15m Database, eu-west-1
Started Jun 23, 2026, 03:16 PM UTC· resolved Jun 23, 2026, 04:32 PM UTC
- investigating Jun 23, 2026, 03:16 PM UTC
We are investigating errors in creating and unpausing projects in the eu-west-1 region.
- identified Jun 23, 2026, 03:26 PM UTC
We have identified the issue is related to keys and are preparing a mitigation.
- identified Jun 23, 2026, 03:43 PM UTC
Multiple mitigations have been deployed and project create performance is improving.
- identified Jun 23, 2026, 03:46 PM UTC
During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect.
- monitoring Jun 23, 2026, 04:01 PM UTC
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.
- resolved Jun 23, 2026, 04:32 PM UTC
Project create and unpause operations have returned to normal and remained stable for the past 30 minutes.
Minor June 23, 2026 Increased latency for Management API requests 58m Dashboard, Management API
Started Jun 23, 2026, 01:21 PM UTC· resolved Jun 23, 2026, 02:19 PM UTC
- identified Jun 23, 2026, 01:21 PM UTC
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 reasons as well. The team has identified the issue and is working on resolution.
- monitoring Jun 23, 2026, 01:39 PM UTC
Latency has returned to normal levels, and we are seeing greatly improved stability across the management API. We are monitoring for any further issues.
- resolved Jun 23, 2026, 02:19 PM UTC
This incident has been resolved.
Minor June 19, 2026 Failed to apply network restrictions 3h 2m
Started Jun 19, 2026, 09:55 PM UTC· resolved Jun 20, 2026, 12:58 AM UTC
- investigating Jun 19, 2026, 09:55 PM UTC
We are aware of some users reporting issues adding new entries to their network restriction lists, and we are currently investigating this issue.
- identified Jun 19, 2026, 10:25 PM UTC
We have identified the root cause of the issue and are actively working on implementing a fix.
- monitoring Jun 19, 2026, 11:39 PM UTC
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.
- monitoring Jun 20, 2026, 12:48 AM UTC
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.
- resolved Jun 20, 2026, 12:58 AM UTC
We are not detecting any remaining network restriction list issues.
Major June 18, 2026 DNS record creation failures impacting project creation, restore, pause 3h 37m
Started Jun 18, 2026, 06:39 AM UTC· resolved Jun 18, 2026, 10:17 AM UTC
- investigating Jun 18, 2026, 06:39 AM UTC
We are investigating DNS Api outage impacting project creation. Impact and details are under review.
- investigating Jun 18, 2026, 07:09 AM UTC
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.
- identified Jun 18, 2026, 07:37 AM UTC
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.
- monitoring Jun 18, 2026, 08:05 AM UTC
We have deployed a fix and are monitoring for full recovery. Project creation, pause and unpause are gradually restored within the next minutes.
- resolved Jun 18, 2026, 10:17 AM UTC
This issue has been resolved and all previous held project updates resumed.
Minor June 17, 2026 Hardware failure in us-east 1h 50m us-east-2
Started Jun 17, 2026, 03:12 PM UTC· resolved Jun 17, 2026, 05:02 PM UTC
- investigating Jun 17, 2026, 03:12 PM UTC
Some projects in US-East-2 are impacted by compute failures in that region. We are actively investigating the issue.
- identified Jun 17, 2026, 03:44 PM UTC
We have identified projects specifically impacted by this issue and are recovering affected projects.
- monitoring Jun 17, 2026, 04:13 PM UTC
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.
- resolved Jun 17, 2026, 05:02 PM UTC
We have now recovered all Projects affected by the outage in us-east-2.
Major June 17, 2026 Degraded Management API performance affecting payments and Supabase Studio 1h 38m API Gateway, Dashboard, ca-central-1, Management API and 3 more
Started Jun 17, 2026, 12:31 PM UTC· resolved Jun 17, 2026, 02:10 PM UTC
- investigating Jun 17, 2026, 12:31 PM UTC
We are currently investigating the issue
- investigating Jun 17, 2026, 12:51 PM UTC
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.
- monitoring Jun 17, 2026, 01:15 PM UTC
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.
- resolved Jun 17, 2026, 02:10 PM UTC
All regions continue to report healthy Management API performance and platform stability.
Minor June 16, 2026 Project usage analytics API endpoints breakage 1h 14m Analytics
Started Jun 16, 2026, 03:47 PM UTC· resolved Jun 16, 2026, 05:01 PM UTC
- investigating Jun 16, 2026, 03:47 PM UTC
We are investigating a breakage in project usage analytics data propagation.
- investigating Jun 16, 2026, 04:18 PM UTC
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.
- identified Jun 16, 2026, 04:22 PM UTC
The component at issue has been identified and we are implementing mitigations. Analytics responsiveness on the impacted endpoint is begining to recover.
- monitoring Jun 16, 2026, 04:27 PM UTC
The mitigation has been successful and analytics endpoints are all responsive. We will continue to monitor for stability.
- resolved Jun 16, 2026, 05:01 PM UTC
All analytics responses have returned to normal.
Minor June 16, 2026 Degraded Log Explorer in the dashboard 3h 42m Analytics
Started Jun 16, 2026, 11:26 AM UTC· resolved Jun 16, 2026, 03:08 PM UTC
- monitoring Jun 16, 2026, 11:26 AM UTC
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.
- identified Jun 16, 2026, 01:01 PM UTC
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.
- monitoring Jun 16, 2026, 01:30 PM UTC
We are seeing things have stabilized across the fleet after further optimization work, and we are monitoring to ensure no further issues arise.
- resolved Jun 16, 2026, 03:08 PM UTC
We have rolled out additional performance improvements to reporting API endpoints.
Minor June 12, 2026 Storage users in US-West-2 experiencing increased latency on storage requests 8h 39m Storage
Started Jun 12, 2026, 04:00 PM UTC· resolved Jun 13, 2026, 12:40 AM UTC
- identified Jun 12, 2026, 04:00 PM UTC
Users in US-West-2 are seeing increased latency on storage requests. The team has identified the issue and is working on a solution.
- identified Jun 12, 2026, 04:30 PM UTC
We are implementing load mitigation strategies to improve the performance of storage requests in US-West-2.
- identified Jun 12, 2026, 05:29 PM UTC
The team is still working on a solution, and mitigation work is underway.
- identified Jun 12, 2026, 06:28 PM UTC
We have implemented further mitigations and are tracking their progress. We continue to actively work this issue.
- identified Jun 12, 2026, 07:30 PM UTC
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.
- monitoring Jun 12, 2026, 08:26 PM UTC
Backlog is being effectively processed and operations have returned to normal. We continue to monitor the performance in us-west-2.
- monitoring Jun 12, 2026, 11:57 PM UTC
Job queues continue to drain. We will actively monitor until they are complete.
- resolved Jun 13, 2026, 12:40 AM UTC
All residual jobs have drained. Storage performance and job activity is normal.
Notice June 10, 2026 Higher connection failure rate for ap-northeast-1 and ap-northeast-2 –
Started Jun 10, 2026, 12:00 AM UTC· resolved Jun 10, 2026, 12:00 AM UTC
- resolved Jun 10, 2026, 01:43 AM UTC
From 00:52 to 01:02 UTC on 10th June an internal deployment in one of the ap-northeast-1 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.
Notice June 8, 2026 DNS Resolution Failures for TLD .co users 8d 4h
Started Jun 08, 2026, 03:39 AM UTC· resolved Jun 16, 2026, 08:16 AM UTC
- identified Jun 08, 2026, 03:39 AM UTC
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.
- monitoring Jun 08, 2026, 06:37 AM UTC
The third-party has confirmed a fix has been implemented and we are validating the results with our impacted users.
- monitoring Jun 08, 2026, 12:38 PM UTC
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.
- monitoring Jun 08, 2026, 05:32 PM UTC
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.
- monitoring Jun 10, 2026, 11:24 PM UTC
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.
- monitoring Jun 12, 2026, 11:09 AM UTC
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.
- monitoring Jun 15, 2026, 04:52 PM UTC
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.
- resolved Jun 16, 2026, 08:16 AM UTC
The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.
Critical June 2, 2026 Errors impacting pause, restore, and backup operations in us-east-2 (Ohio) 1h 5m Management API
Started Jun 02, 2026, 01:36 PM UTC· resolved Jun 02, 2026, 02:41 PM UTC
- investigating Jun 02, 2026, 01:36 PM UTC
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.
- identified Jun 02, 2026, 02:05 PM UTC
We have identified the cause is related to a recent deployment. We have initiated a redeploy to address the issue.
- monitoring Jun 02, 2026, 02:12 PM UTC
The redeployment has returned pause, restore and backup operations in the affected region to normal. We will continue to monitor for any residual impact.
- resolved Jun 02, 2026, 02:41 PM UTC
All operations have continued as normal since moving this incident to Monitoring. We are resolving this incident.
Minor May 21, 2026 Branch creation degradation 2h 39m
Started May 21, 2026, 04:46 PM UTC· resolved May 21, 2026, 07:26 PM UTC
- investigating May 21, 2026, 04:46 PM UTC
We are seeing degradation in branch creation linked to database migration locks. We are investigating and will share further updates as progress is made.
- investigating May 21, 2026, 05:45 PM UTC
We continue investigating different possible underlying causes and will provide updates as progress is made.
- monitoring May 21, 2026, 06:54 PM UTC
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.
- resolved May 21, 2026, 07:26 PM UTC
Branch creation continues to be stable.
Minor May 21, 2026 Login issues for SSO and Email accounts on Supabase Dashboard 2h 20m Dashboard
Started May 21, 2026, 08:30 AM UTC· resolved May 21, 2026, 10:51 AM UTC
- investigating May 21, 2026, 08:30 AM UTC
Users that are already logged in are not affected.
- investigating May 21, 2026, 08:33 AM UTC
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.
- identified May 21, 2026, 08:49 AM UTC
We have identified the issue as being related to a recent key rotation and are currently working on a fix.
- identified May 21, 2026, 09:26 AM UTC
A fix has been implemented and is currently being rolled out. We will continue to provide updates as the deployment progresses.
- monitoring May 21, 2026, 09:43 AM UTC
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.
- resolved May 21, 2026, 10:51 AM UTC
The issue affecting SSO logins has now been resolved. Thank you for your patience while we worked through this issue.
Minor May 20, 2026 Network restrictions preventing read replica communication 7h 40m Database
Started May 20, 2026, 09:04 PM UTC· resolved May 21, 2026, 04:44 AM UTC
- investigating May 20, 2026, 09:04 PM UTC
Network restrictions are preventing read replicas from communicating with their primaries for a limited number of customer projects. We are actively investigating this issue.
- investigating May 20, 2026, 09:46 PM UTC
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.
- identified May 20, 2026, 10:48 PM UTC
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.
- identified May 20, 2026, 11:41 PM UTC
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.
- identified May 21, 2026, 01:12 AM UTC
Our team continues to work on implementing a fix for the issue. We will provide additional updates as progress is made.
- identified May 21, 2026, 03:49 AM UTC
We have developed a fix and it is currently being validated. We will provide more updates soon.
- monitoring May 21, 2026, 04:23 AM UTC
We have merged the fix and are monitoring for stability.
- resolved May 21, 2026, 04:44 AM UTC
Communication between read replicas and their primaries for impacted projects has been restored. This incident is now resolved.
Minor May 20, 2026 Paused Projects Showing Incorrect Resume Deadline 4h Dashboard
Started May 20, 2026, 03:40 PM UTC· resolved May 20, 2026, 07:41 PM UTC
- investigating May 20, 2026, 03:40 PM UTC
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.
- identified May 20, 2026, 04:17 PM UTC
We’ve isolated the cause of the issue to a recent change and are working on reverting it now.
- identified May 20, 2026, 05:41 PM UTC
The revert of the change is in process.
- monitoring May 20, 2026, 07:11 PM UTC
This change has been reverted. We are monitoring to ensure things remain stable.
- resolved May 20, 2026, 07:41 PM UTC
The UI message incident has been resolved.
Minor May 18, 2026 Log ingestion issues 43m Analytics
Started May 18, 2026, 11:26 PM UTC· resolved May 19, 2026, 12:10 AM UTC
- investigating May 18, 2026, 11:26 PM UTC
Customers may experience delayed log ingestion or periods where logs are unavailable. We will provide updates while we work to resolve the issue.
- monitoring May 18, 2026, 11:58 PM UTC
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.
- resolved May 19, 2026, 12:10 AM UTC
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.
Notice May 15, 2026 Auth Service Update 1h 7m Auth
Started May 15, 2026, 06:11 PM UTC· resolved May 15, 2026, 07:18 PM UTC
- identified May 15, 2026, 06:11 PM UTC
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.
- monitoring May 15, 2026, 06:47 PM UTC
The update has been implemented. Service changes can be made. We will monitor the effect for the next 30 minutes to ensure stability.
- resolved May 15, 2026, 07:18 PM UTC
All changes hav been applied.
Notice May 14, 2026 Access Issues From Some Providers in Brazil 32d 16h
Started May 14, 2026, 03:34 PM UTC· resolved Jun 16, 2026, 08:15 AM UTC
- investigating May 14, 2026, 03:34 PM UTC
We are investigating reports of some access issues to Supabase IP addresses from a network provider in Brazil.
- investigating May 14, 2026, 03:54 PM UTC
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.
- investigating May 14, 2026, 04:37 PM UTC
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.
- identified May 14, 2026, 10:23 PM UTC
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.
- identified May 19, 2026, 10:30 PM UTC
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.
- identified Jun 03, 2026, 09:32 PM UTC
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.
- identified Jun 09, 2026, 01:26 PM UTC
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.
- monitoring Jun 12, 2026, 02:42 PM UTC
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.
- monitoring Jun 15, 2026, 04:52 PM UTC
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.
- resolved Jun 16, 2026, 08:15 AM UTC
The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.
Minor May 14, 2026 Reports of issues connecting to API Endpoints 44m API Gateway
Started May 14, 2026, 02:56 PM UTC· resolved May 14, 2026, 03:40 PM UTC
- investigating May 14, 2026, 02:56 PM UTC
We are investigating reports of connectivity issues to project API endpoints.
Minor May 13, 2026 Edge Traffic Issues 4h 19m Edge Functions
Started May 13, 2026, 04:15 PM UTC· resolved May 13, 2026, 08:35 PM UTC
- investigating May 13, 2026, 04:15 PM UTC
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.
- investigating May 13, 2026, 04:46 PM UTC
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.
- investigating May 13, 2026, 05:31 PM UTC
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.
- identified May 13, 2026, 07:50 PM UTC
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.
- resolved May 13, 2026, 08:35 PM UTC
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
Minor May 9, 2026 Error spikes in one of the eu-central-1 Supavisor clusters –
Started May 09, 2026, 03:00 PM UTC· resolved May 09, 2026, 03:00 PM UTC
- resolved May 19, 2026, 10:31 AM UTC
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
Minor May 8, 2026 Customer Projects Experiencing Upgrade Issues 2h 48m
Started May 08, 2026, 01:25 PM UTC· resolved May 08, 2026, 04:13 PM UTC
- identified May 08, 2026, 01:25 PM UTC
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.
- identified May 08, 2026, 01:26 PM UTC
We are continuing to work on a fix for this issue.
- identified May 08, 2026, 01:46 PM UTC
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.
- monitoring May 08, 2026, 02:39 PM UTC
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.
- resolved May 08, 2026, 04:13 PM UTC
Upgrade operations have returned to normal.