Supabase Status

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.

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

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.