Connection issues in Supavisor us-east-1 cluster
Monitoring - We believe the issue has resolved. We are monitoring for any recurrence.
Jun 30, 2026 - 17:06 UTC
Investigating - 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.
Jun 30, 2026 - 16:56 UTC
Project status change failures in multiple regions
Update - 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.
Jun 30, 2026 - 11:20 UTC
Update - 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.
Jun 30, 2026 - 06:49 UTC
Update - 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.
Jun 30, 2026 - 05:11 UTC
Update - We are continuing to work on a fix for the issue and will provide updates as more information is available.
Jun 30, 2026 - 04:32 UTC
Identified - 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.
Jun 30, 2026 - 03:38 UTC
Update - 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.
Jun 30, 2026 - 03:08 UTC
Update - Project creation is impacted across multiple regions, we are investigating the root cause.
Jun 30, 2026 - 02:43 UTC
Investigating - We are currently investigating an issue affecting project creation in multiple regions.
Jun 30, 2026 - 02:38 UTC
Uptime over the past 90 days. View historical uptime.
Compute capacity Operational
ap-northeast-1 Operational
ap-northeast-2 Operational
ap-south-1 Operational
ap-southeast-1 Operational
ap-southeast-2 Operational
ca-central-1 Operational
eu-central-1 Operational
eu-central-2 Operational
eu-north-1 Operational
eu-west-1 Operational
eu-west-2 Operational
eu-west-3 Operational
sa-east-1 Operational
us-east-1 Operational
us-east-2 Operational
us-west-1 Operational
Analytics Operational
90 days ago
99.97 % uptime
Today
API Gateway Operational
90 days ago
99.9 % uptime
Today
Auth Operational
90 days ago
99.84 % uptime
Today
Connection Pooler Operational
90 days ago
100.0 % uptime
Today
Dashboard Operational
90 days ago
99.88 % uptime
Today
Database Operational
90 days ago
99.86 % uptime
Today
Edge Functions Operational
90 days ago
99.92 % uptime
Today
Management API Operational
90 days ago
99.94 % uptime
Today
Realtime Operational
90 days ago
99.92 % uptime
Today
Storage Operational
90 days ago
99.92 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Scheduled Platform Maintenance 07/02 Jul 2, 2026 03:00-04:00 UTC

We will be carrying out a scheduled maintenance window to perform internal platform improvements and upgrades.

Maintenance Window:
- Start time: 03:00 UTC on July 2, 2026
- End time: 04:00 UTC on July 2, 2026

Impact:
- Various platform operations will be delayed during this window
- These may include project creation and initial configuration/setup
- All affected operations will be rescheduled at the end of the window to ensure no operation is dropped
Posted on Jun 29, 2026 - 16:56 UTC
System Metrics Month Week Day
REST API Latency (Singapore)
Fetching
REST API Latency (North Virginia)
Fetching
REST API Latency (Frankfurt)
Fetching
Jun 30, 2026

Unresolved incidents: Connection issues in Supavisor us-east-1 cluster, Project status change failures in multiple regions.

Jun 29, 2026

No incidents reported.

Jun 28, 2026

No incidents reported.

Jun 27, 2026

No incidents reported.

Jun 26, 2026
Scheduled Platform Maintenance 06/26
Completed - The scheduled maintenance has been completed.
Jun 26, 04:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 26, 03:00 UTC
Scheduled - We will be carrying out a scheduled maintenance window to perform internal platform improvements and upgrades.

Maintenance Window:
- Start time: 03:00 UTC on June 26, 2026
- End time: 04:00 UTC on June 26, 2026

Impact:
- Various platform operations will be delayed during this window
- These may include project creation and initial configuration/setup
- All affected operations will be rescheduled at the end of the window to ensure no operation is dropped
Jun 22, 14:12 UTC
Jun 25, 2026
Upgrade Failures
Resolved - Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved.
Jun 25, 18:51 UTC
Monitoring - 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.
Jun 25, 18:08 UTC
Update - 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.
Jun 25, 17:46 UTC
Update - We are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems.
Jun 25, 17:03 UTC
Update - We are implementing operational mitigations to try to improve upgrade performance.
Jun 25, 16:27 UTC
Update - 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.
Jun 25, 16:03 UTC
Update - We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades.
Jun 25, 15:32 UTC
Identified - The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources.
Jun 25, 15:01 UTC
Update - Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays.
Jun 25, 14:41 UTC
Investigating - We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps.
Jun 25, 14:20 UTC
Elevated errors on Postgres change subscriptions
Resolved - We have confirmed that the fix has been successfully applied and the issue affecting Postgres Change subscriptions has been resolved. We will continue to monitor the service, but all systems are operating normally at this time.
Jun 25, 02:16 UTC
Monitoring - We have applied a fix and are monitoring the results to ensure the issue is fully resolved.
Jun 25, 00:49 UTC
Identified - 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.
Jun 24, 23:58 UTC
Investigating - 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.
Jun 24, 23:52 UTC
Jun 24, 2026
Degraded performance of the Shared Pooler cluster in ap-southeast-1
Resolved - 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.
Jun 24, 16:14 UTC
Investigating - 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.
Jun 24, 15:59 UTC
Jun 23, 2026
Project create and unpause errors in eu-west-1
Resolved - Project create and unpause operations have returned to normal and remained stable for the past 30 minutes.
Jun 23, 16:32 UTC
Monitoring - 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.
Jun 23, 16:01 UTC
Update - During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect.
Jun 23, 15:46 UTC
Update - Multiple mitigations have been deployed and project create performance is improving.
Jun 23, 15:43 UTC
Identified - We have identified the issue is related to keys and are preparing a mitigation.
Jun 23, 15:26 UTC
Investigating - We are investigating errors in creating and unpausing projects in the eu-west-1 region.
Jun 23, 15:16 UTC
Increased latency for Management API requests
Resolved - This incident has been resolved.
Jun 23, 14:19 UTC
Monitoring - Latency has returned to normal levels, and we are seeing greatly improved stability across the management API. We are monitoring for any further issues.
Jun 23, 13:39 UTC
Identified - 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.
Jun 23, 13:21 UTC
Jun 22, 2026

No incidents reported.

Jun 21, 2026

No incidents reported.

Jun 20, 2026
Failed to apply network restrictions
Resolved - We are not detecting any remaining network restriction list issues.
Jun 20, 00:58 UTC
Update - 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.
Jun 20, 00:48 UTC
Monitoring - 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.
Jun 19, 23:39 UTC
Identified - We have identified the root cause of the issue and are actively working on implementing a fix.
Jun 19, 22:25 UTC
Investigating - We are aware of some users reporting issues adding new entries to their network restriction lists, and we are currently investigating this issue.
Jun 19, 21:55 UTC
Jun 19, 2026
Jun 18, 2026
DNS record creation failures impacting project creation, restore, pause
Resolved - This issue has been resolved and all previous held project updates resumed.
Jun 18, 10:17 UTC
Monitoring - We have deployed a fix and are monitoring for full recovery. Project creation, pause and unpause are gradually restored within the next minutes.
Jun 18, 08:05 UTC
Identified - 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.
Jun 18, 07:37 UTC
Update - 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.
Jun 18, 07:09 UTC
Investigating - We are investigating DNS Api outage impacting project creation. Impact and details are under review.
Jun 18, 06:39 UTC
Jun 17, 2026
Hardware failure in us-east
Resolved - We have now recovered all Projects affected by the outage in us-east-2.
Jun 17, 17:02 UTC
Monitoring - 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.
Jun 17, 16:13 UTC
Identified - We have identified projects specifically impacted by this issue and are recovering affected projects.
Jun 17, 15:44 UTC
Investigating - Some projects in US-East-2 are impacted by compute failures in that region. We are actively investigating the issue.
Jun 17, 15:12 UTC
Degraded Management API performance affecting payments and Supabase Studio
Resolved - All regions continue to report healthy Management API performance and platform stability.
Jun 17, 14:10 UTC
Monitoring - 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.
Jun 17, 13:15 UTC
Update - 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.
Jun 17, 12:51 UTC
Investigating - We are currently investigating the issue
Jun 17, 12:31 UTC
Jun 16, 2026
Project usage analytics API endpoints breakage
Resolved - All analytics responses have returned to normal.
Jun 16, 17:01 UTC
Monitoring - The mitigation has been successful and analytics endpoints are all responsive. We will continue to monitor for stability.
Jun 16, 16:27 UTC
Identified - The component at issue has been identified and we are implementing mitigations. Analytics responsiveness on the impacted endpoint is begining to recover.
Jun 16, 16:22 UTC
Update - 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.
Jun 16, 16:18 UTC
Investigating - We are investigating a breakage in project usage analytics data propagation.
Jun 16, 15:47 UTC
Degraded Log Explorer in the dashboard
Resolved - We have rolled out additional performance improvements to reporting API endpoints.
Jun 16, 15:08 UTC
Monitoring - We are seeing things have stabilized across the fleet after further optimization work, and we are monitoring to ensure no further issues arise.
Jun 16, 13:30 UTC
Identified - 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.
Jun 16, 13:01 UTC
Monitoring - 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.
Jun 16, 11:26 UTC
DNS Resolution Failures for TLD .co users
Resolved - The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.
Jun 16, 08:16 UTC
Update - 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.
Jun 15, 16:52 UTC
Update - 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.
Jun 12, 11:09 UTC
Update - 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.
Jun 10, 23:24 UTC
Update - 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.
Jun 8, 17:32 UTC
Update - 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.
Jun 8, 12:38 UTC
Monitoring - The third-party has confirmed a fix has been implemented and we are validating the results with our impacted users.
Jun 8, 06:37 UTC
Identified - 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.
Jun 8, 03:39 UTC
Access Issues From Some Providers in Brazil
Resolved - The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.
Jun 16, 08:15 UTC
Update - 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.
Jun 15, 16:52 UTC
Monitoring - 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.
Jun 12, 14:42 UTC
Update - 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.
Jun 9, 13:26 UTC
Update - 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.
Jun 3, 21:32 UTC
Update - 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.
May 19, 22:30 UTC
Identified - 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.
May 14, 22:23 UTC
Update - 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.
May 14, 16:37 UTC
Update - 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.
May 14, 15:54 UTC
Investigating - We are investigating reports of some access issues to Supabase IP addresses from a network provider in Brazil.
May 14, 15:34 UTC
← Incident History Powered by Atlassian Statuspage