Looking for an update now? Check the current status, or follow Supabase for future changes.
12.2%of 49 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
0%
30
30
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 14Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.
identified
A fix has been developed and we are going through the review and implementation process.
identified
We have identified the issue with the upgrade. To prevent issues, we have suspended the ability to upgrade projects while we resolve this issue. The problem is limited to upgrades from earlier versions of PG17 to the most recent release. We are working on a fix.
investigating
We have observed failures in attempted upgrades to 17.11.0.003. We are investigating.
Increased errors on management api leading to project operation failures
We have identified a rollout causing error increase on management api dependant services, which is causing project operation failures and FGA Authentication errors across multiple functions.
We have implementing a fix and observing recovery. Our teams are continuing to monitor for full resolution.
investigating
We are continuing to investigate this issue.
investigating
We are investigating an increase in errors on project update flows including creation, pausing/unpausing and upgrading across multiple regions.
A fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully resolving this incident.
identified
While we have observed significant improvement in rates of high latency, we note that some users are still experiencing issues during peak Eastern US business hours. We continue to work with our networking partners to isolate and resolve any lingering sources of high latency. We recognize that this is a longstanding issue and appreciate the patience of affected customers. We will continue to share additional updates here as soon as they are available.
identified
Our networking partners have implemented a mitigation to the latency issue at the problematic PoP in the Eastern US, and we have since observed significant improvement in rates of high latency across the region. We are continuing to work with those partners to isolate any additional root causes of latency and improve the reliability of our networking infrastructure across the region.
identified
We are seeing signs of improvement and are continuing to work alongside our networking partners towards a resolution.
We will provide another update as more information becomes available.
identified
We're continuing to coordinate with our networking partners to deliver a permanent resolution.
We will provide updates as soon as they're available.
identified
We are working with our networking partners on a permanent fix.
While we do not have an estimated resolution time, we will share updates here as they become available.
identified
A mitigation for this issue was applied earlier today, but we do not have sufficient evidence to conclude that the mitigation resulted in improvement to this eastern US latency issue. We have tied the issue to a particular PoP, and we are continuing to work with our networking partners to bring this issue to a final resolution. We will provide another update within 4 hours, if not before. We appreciate your patience.
identified
We are continuing our work to fix this latency issue, which has been observed to impact clients connecting to Supabase Projects from the eastern United States. These clients may include servers and serverless functions located in that geographical region, regardless of the region in which the Project is hosted.
identified
We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks.
We are actively working on a fix. We will provide updates as the fix is implemented.
We are continuing to monitor to ensure ongoing stability.
identified
The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.
identified
Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon.
This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available.
identified
All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.
identified
We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.
investigating
We are investigating project lifecycle operation issues in eu-west-1.
We have applied a fix, and administrative operations in the Supabase Dashboard are now completing as expected.
We are monitoring the results to ensure the issue is fully resolved.
identified
We have identified the issue causing some users to encounter permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard.
We are working on a fix and will provide another update once it has been implemented.
investigating
We are investigating reports of users encountering permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard.
This may prevent some users from managing their projects through the Dashboard.
We are working to identify the cause and will provide further updates as they become available.
We are no longer seeing rate limiting issues affecting Supabase CLI CI workflows. We're continuing to monitor the service for stability while we roll out a fallback patch to improve resilience and help prevent the issue from recurring.
identified
We've identified the cause and are working on a fix.
A fix has been implemented for the affected tenants and we are monitoring the results. We will continue to monitor the situation and will provide further updates as more information becomes available.
investigating
We have identified an issue with Storage for projects are restoring from backups. Users may experience increased 500 errors.
We are working to identify the root cause and will notify for any progress as soon as we have an update
Increased error rate in project creation and project restore
A fix has been implemented and we are monitoring the results.
identified
We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.
investigating
We are currently investigating this issue
Supavisor connection disruptions in EU West 1 (Ireland)
The affected Supavisor node has been restarted, and error rates have returned to normal levels.
We’ll continue to monitor the service to ensure stability.
investigating
Some projects in the EU West 1 (Ireland) region may experience disruptions to Supavisor connections.
Our team is aware of the issue and actively working on a resolution.
We’ll share further updates as they become available.
Legacy Incident Archive
80 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
DNS record creation failures impacting project creation, restore, pause
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have deployed a fix and are monitoring for full recovery. Project creation, pause and unpause are gradually restored within the next minutes.
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.
investigating
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.
investigating
We are investigating DNS Api outage impacting project creation. Impact and details are under review.
Hardware failure in us-east
minorSource not attested
Last archived state: resolved
View archived record details
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.
identified
We have identified projects specifically impacted by this issue and are recovering affected projects.
investigating
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
majorSource not attested
Last archived state: resolved
View archived record details
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.
investigating
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...
investigating
We are currently investigating the issue
Project usage analytics API endpoints breakage
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The mitigation has been successful and analytics endpoints are all responsive. We will continue to monitor for stability.
identified
The component at issue has been identified and we are implementing mitigations. Analytics responsiveness on the impacted endpoint is begining to recover.
investigating
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.
investigating
We are investigating a breakage in project usage analytics data propagation.
Degraded Log Explorer in the dashboard
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are seeing things have stabilized across the fleet after further optimization work, and we are monitoring to ensure no further issues arise.
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.
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.
Storage users in US-West-2 experiencing increased latency on storage requests
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Job queues continue to drain. We will actively monitor until they are complete.
monitoring
Backlog is being effectively processed and operations have returned to normal. We continue to monitor the performance in us-west-2.
identified
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.
identified
We have implemented further mitigations and are tracking their progress. We continue to actively work this issue.
identified
The team is still working on a solution, and mitigation work is underway.
identified
We are implementing load mitigation strategies to improve the performance of storage requests in US-West-2.
identified
Users in US-West-2 are seeing increased latency on storage requests. The team has identified the issue and is working on a solution.
DNS Resolution Failures for TLD .co users
Source not attested
Last archived state: resolved
View archived record details
monitoring
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.
monitoring
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...
monitoring
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
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
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
The third-party has confirmed a fix has been implemented and we are validating the results with our impacted users.
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.
Errors impacting pause, restore, and backup operations in us-east-2 (Ohio)
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
The redeployment has returned pause, restore and backup operations in the affected region to normal. We will continue to monitor for any residual impact.
identified
We have identified the cause is related to a recent deployment. We have initiated a redeploy to address the issue.
investigating
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
Branch creation degradation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
We continue investigating different possible underlying causes and will provide updates as progress is made.
investigating
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
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
identified
A fix has been implemented and is currently being rolled out. We will continue to provide updates as the deployment progresses.
identified
We have identified the issue as being related to a recent key rotation and are currently working on a fix.
investigating
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.
investigating
Users that are already logged in are not affected.
