Looking for an update now? Check the current status, or follow Supabase for future changes.
10.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
A fix has been rolled out across all regions, and results are positive.
We will continue monitoring to ensure the service remains stable.
Moving this incident to monitoring.
identified
An enhanced automated solution is currently being tested in staging.
It is expected to be more effective and efficient than the approach used previously.
Once testing has completed successfully, we will use this approach to roll out the fix in production.
We will provide further updates as this work progresses.
identified
We are continuing to rollout the fix to further regions.
identified
This issue is fixed in eu-central-2 and ap-south-1. We are continuing to rollout the fix to all regions.
investigating
Some users on Project versions 15.1 and older are experiencing a pgBouncer configuration issue causing connection issues for the Dedicated Pooler and Storage services. We are continuing our investigation of this issue.
investigating
Some users on older Projects are experiencing a pgBouncer configuration issue causing connection issues for the Dedicated Pooler and Storage services. This issue should only affect users with Project versions 15.1 and older. We have determined the cause of this issue and we are rolling out a fix.
The deployment process changes have been rolled out across all regions. We will monitor throughout the weekend.
The new Supabase version will be released early next week. Once it is released, impacted users can upgrade to from their dashboard to resolve this issue.
Thank you again for your patience while we worked through this. We will provide an update once the new version is available and users can upgrade.
identified
We have rolled out the deployment process changes to eu-central-2 and continue to monitor. We will provide additional updates as we make this change to other regions.
Once this change is implemented across all regions, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue.
identified
To resolve this issue, our fleet requires a change to our deploy process. We have spent this week making these changes and will be implementing them throughout this weekend, starting on Friday, September 18. Once this change is implemented, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue.
We recognize that this is added work for our customers. This issue has been open for over a month, as we tried to make this change on each project's behalf. In an effort to resolve this sooner, we have opted to make this deployment process change and ask users to upgrade.
identified
We continue to monitor progress and are slowly updating each region. Thank you for your patience on this issue.
identified
Testing results have been positive.
Following some additional checks today, we plan to expand the rollout.
We’ll continue to monitor progress and provide further updates as they become available.
identified
A stale time cache has been identified as the cause of this issue. A targeted fix has been written and is undergoing internal testing. It will be rolled out when testing is complete. Thank you for your patience while we investigated this issue. We will update the status page when the fix is rolled out.
identified
We have seen reports that the JWT rejection issue persisted with 14.17, and due to <a href="https://status.supabase.com/incidents/bv4ntm4x0btf">some unintended performance side effects</a>, we have rolled back to Postgrest 14.5. The team continues to investigate the JWT issue and hopes to have a solution soon.
identified
We continue to monitor the fixes introduced by this latest rollout. If you are continuing to see these errors, some customers have reported that restarting their project after the rollout resolved this issue.
To restart your project, go to the General settings page in the dashboard and select Restart project.
Please contact our support team if the issue persists after a restart.
identified
PostgREST 14.17 has now been rolled out to all regions.
Some customers have reported that restarting their project after the rollout resolved this issue.
To restart your project, go to the General settings page in the dashboard and select Restart project.
Please contact our support team if the issue persists after a restart.
identified
We are continuing to rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful.
This fix has been applied to the following regions:
ap-east-1
ap-northeast-1
ap-northeast-2
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
eu-central-1
eu-central-2
eu-north-1
eu-west-2
eu-west-3
We will continue rolling out this fix to the remaining regions throughout this week and provide updates as more regions are successful.
identified
We are continuing to test and rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful.
We will monitor eu-central-2 over the weekend and are preparing for the fix to be pushed to all regions starting Monday. Thank you for your patience while we've worked on multiple fixes for this issue.
identified
As part of the incident remediation flow, we have separately identified "/lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found" error between 11:15 - 16:24 UTC today affecting PostgREST. This has been fixed and we can see the error rates have subsided.
identified
Fixes for this issue are being sequentially rolled out. The impact of the issue is limited to a subset of new projects that can experience it upon some JWT renewals. We will update the status when all the fix rollouts have completed.
identified
Our teams are continuing to work on the fix and rollout is underway for selected customers. We will provide another update as we are applying the fix to all impacted users.
identified
We have identified the root cause of newly refreshed JWTs being rejected by the API, resulting in HTTP 401 errors for affected sessions. We are working on a fix and will provide updates as things progress.
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.
