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
Incident History
September 2026
Project creations are degraded in multiple regions
We have identified increased latency in Project creations in these regions from 0730 UTC to 0805 UTC:
ap-northeast-1
ap-northeast-2
eu-central-1
eu-central-2
eu-north-1
eu-west-1
eu-west-3
us-west-1
The latency has since recovered and our teams are monitoring for full recovery.
Existing project availability has not been impacted.
The fix has been rolled out to us-east-1. We will continue to monitor both regions for stability.
identified
The fix has been implemented for ap-northeast-2 and we're working on implementing the fix for us-east-1. We will continue to provide updates as progress is made.
identified
We are continuing to work on a fix and will provide updates as things progress.
identified
Projects running Postgres version 14 in us-east-1 and ap-northeast-2 may experience query slowness. We've identified the cause and are working on a fix.
Error rates have returned to normal, and the service is operating as expected.
The team continues to investigate the underlying cause of the latency and spike in 503 errors.
investigating
We are investigating reports of increased Edge Function latency and elevated rates of HTTP 503 responses, beginning at approximately 06:00 UTC.
Our team is working to identify the cause and will provide further updates as they become available.
We have rolled out a fix across all regions and are continuing to monitor over the next few hours.
Due to this incident, impacted users who's project were compute constrained would have received a 'Your Supabase Project <Name> is running out of Disk IO Budget' email which is no longer valid. No further action is required and your project availability should be restored to normal.
monitoring
We have rolled out a fix across all regions and are continuing to monitor over the next few hours.
Users still affected by project outages are encouraged to restart their projects which has shown to resolve lasting errors.
identified
We have rolled out a version of the fix across all regions that will prevent recurrence of the issue. Users still affected by project outages are encouraged to restart their projects.
identified
Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.
identified
A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.
identified
We have identified why projects are becoming unresponsive and are implementing a mitigation.
investigating
We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.
Project Lifecycle Actions Showing increased error rates across all regions
Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.
We are going to monitor to ensure that things stay stable. The team is working through any remaining projects which did not automatically resolve.
Some users may also notice that backups will happen a bit later than usual, but these jobs are running and completing normally.
identified
We've increased project lifecycle operations to 50% of users and things are holding steady. We're continuing to ramp this up until operations are restored for all users.
This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.
Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
identified
Error rates have returned to normal, and the backlogs are draining well. We are beginning to slowly re-enable lifecycle operations for users.
We will be monitoring impact, and we hope to have this re-enabled everywhere soon. We will leave this in this state until lifecycle operations have been completely restored.
Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
identified
We are seeing incremental improvements internally. There is a large backlog of actions that we are working through, but things are progressing. Once we make it through most of the backlog, we will re-enable lifecycle actions.
This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.
Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
identified
The team is continuing to work on restoring project lifecycle operations. Out of caution, we have disabled lifecycle operations.
This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.
Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
We will provide additional updates as we have more information.
identified
The team has applied a fix, but error rates remain high. We are continuing to work and will take other necessary steps to resolve this as soon as possible.
Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved: Creates, Configuration changes, Restarts, or Compute size changes. We will provide additional updates as we have ...
identified
We have identified the source of the errors with project lifecycle actions, and the team is currently working to resolve it.
This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.
Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provid...
investigating
We are seeing increased error rates in actions across all project lifecycle actions - Creations, Deletions, Restores, Configuration and Compute size upgrades. We are currently looking into the cause.
Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information
A recent change affected users ability to log in to the Supabase Dashboard.
We’ve reverted the change, and testing indicates that the issue is resolved.
Please try logging in again. If you’re still unable to log in, perform a full browser refresh and retry.
Projects and non-Dashboard traffic remained unaffected.
investigating
We’re investigating an issue preventing users from logging in to the Supabase Dashboard.
Users who were logged into the dashboard were logged out.
Dashboard actions are currently not available.
Projects remain online and available. Non-Dashboard traffic is not impacted.
We’ll share another update as soon as we have more information.
investigating
We are currently investigating an issue where users are unable to login to the Supabase dashboard
Project creation is reporting as recovered across the platform. We will monitor for stability in the near term.
identified
We are seeing the mitigation steps having the desired effect. Project creation is recovering.
investigating
While the first set of actions are taking effect, we are implementing a second set of likely mitigations to attempt to facilitate improvement in project creation.
investigating
We continue to work this issue. The steps we have taken are addressing the hypothesized cause of the issue. We are implementing further related mitigations.
investigating
We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance.
investigating
Project creation is failing for new projects on the platform. We are investigating.
Response times have recovered in all regions. We will continue to monitor throughout the weekend.
monitoring
The rollout has been completed in all regions. We will continue to monitor.
identified
The roll out has also been completed for us-east-1.
identified
PostgREST 14.5 has been deployed since 12:00pm UTC to all AP regions: ap-east-1, ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, and ap-southeast-2
as well as sa-east-1 and ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-west-2, and eu-west-3, us-west-1
We'll continue to provide updates as we roll out the change for the remaining impacted regions.
identified
We are continuing to work through the remediation plan for the latency issues.
We will provide a further update as soon as more information is available.
identified
The team has identified the change which resulted in additional latency and error rates for some data API Requests. They are preparing to roll this change back. This rollout will take some time, and we will update again as there is news on the progress of the fix.
investigating
We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
investigating
We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
investigating
We’re continuing to investigate the issue causing increased response times for requests and 525 errors. Our team remains actively engaged in the investigation, we’ll provide another update as soon as we have more details.
investigating
We’re currently investigating latency issue that may cause increased response times for a small percentage of requests. In some cases, this may also result in 525 errors.
Our team is actively working to resolve the issue. We’ll share another update as soon as we have more information.
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.
