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.
August 2026
Increased rates of Pooler connection timeouts in us-east-1
Source not attested
Last archived state: resolved
View archived record details
Connection Pooler
monitoring
We have identified a degraded Supavisor node and we have rolled out a fix. We are monitoring to ensure continued stability.
investigating
We are aware of reports of increased rates of connection timeouts for users connecting to Projects in us-east-1 via Supavisor.
A fix has been applied, and the issue is now resolved. We are moving the incident to monitoring.
We will continue to follow up directly with affected users who opened a support ticket.
investigating
We are investigating an issue affecting automatic disk resizing.
Some projects may experience delays before a resize is completed, while others may see repeated or duplicate resize operations.
We are working to identify the cause and will provide an update as soon as we have more information.
Error spikes in one of the ap-northeast-2 Supavisor clusters
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have applied a fix and are monitoring for full resolution. Errors have ceased in the last minutes and all connections are back to healthy.
investigating
We are continuing to investigate the errors in ap-northeast-2 Supavisor clusters.
investigating
We are investigating error spikes in the ap-northeast-2 Supavisor clusters.
Users reported failures in connecting to postgres via Supavisor with the error: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode.
Delays in project provisioning
Source not attested
Last archived state: resolved
View archived record details
monitoring
We've applied a fix for the issue affecting project pause/restore, branch creation, and project provisioning across multiple regions.
Errors related to branch creation have dropped, and we're continuing to monitor to confirm full recovery. We'll share another update once we've confirmed the issue is resolved.
identified
We've identified the issue causing delays and failures in project pause/restore, branch creation, and project provisioning across multiple regions.
Branch creation is currently failing for affected users, and project provisioning may be delayed. We're continuing to work on a fix and will share the next update as we have more information.
investigating
We're investigating delays affecting project pause/restore, branch creation, and project provisioning across multiple regions. Some users may see failures or slowness when performing these operations. We'll share updates as we learn more.
Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've identified that starting 4pm UTC on August 18th we began seeing sign-in failures with signInWithIdToken (OIDC) logins on free-tier projects. Users authenticating with OIDC providers other than Google/Apple/Firebase may have seen failed login attempts.
We've identified the root cause and fix has been rolled out. We are monitoring for continued stability.
monitoring
We've identified that starting 4pm UTC on August 18th we began seeing sign-in failures with signInWithIdToken (OIDC) logins on free-tier projects. Users authenticating with OIDC providers other than Google/Apple/Firebase may have seen failed login attempts.
We've identified the root cause and fix has been rolled out.
monitoring
We've identified an issue causing sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects. Users authenticating with non-Google/Apple/Firebase OIDC providers may see failed login attempts.
We've identified the root cause and fix has been rolled out.
Impacted timeframe was 18th August 4pm UTC - 19th Aug 10:30am UTC
Project creation failing in selected regions
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating an issue with project creation failing. We will be confirming more information shortly.
Project access, updating and creation impacted in us-east-2
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been applied to all impacted projects in us-east-2. We are monitoring for full resolution.
identified
A fix is being rolled out and we are seeing improved performance across impacted projects. We are continuing to roll out the full fix and will be confirming recovery asap.
identified
We are investigating an issue of project creation and updating in us-east-2. A fix is under review and prepared for being rolled out.
MCP connection error to branch environments
Source not attested
Last archived state: resolved
View archived record details
monitoring
We have pushed a fix to address the root cause and are monitoring the situation. If you continue to see an error, you can re-authenticate with the Supabase MCP server and also confirm that you have access to the preview branch.
monitoring
UPDATE: We are currently pushing a fix to address the root cause. We'll provide another update once the fix has been fully deployed.
identified
We're still working on implementing a fix for the identified root cause.
identified
We've identified the root cause that was leading to permission errors on MCP connections to branch environments. We're currently working on addressing this.
investigating
We're currently investigating an issue that is impacting MCP connections to branch environments.
Project Upgrade Delays
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have deployed a tested fix for the upgrade issue impacting some projects. The fix has been effective and we are monitoring for continued stability.
identified
We are continuing to test the fix to project upgrades. We will update again when the fix is applied.
identified
The team has identified a likely fix and is consolidating the details in order to move to thorough testing. We will update again when the fix is applied.
identified
We are continuing to fix project upgrade issues and are investigating further remediation. We will provide our next update within the next 14 hours.
identified
We are developing a fix for the upgrade issues.
identified
We have identified the cause of the upgrade delays and are working on a fix.
investigating
We are continuing to investigate project upgrade issues.
investigating
We are investigating a potential issue that could result in a delay or failure in some users' project upgrades.
July 2026
Management API Performance Degradation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor the the Management API to ensure no further intermittent occurrences appear. We will provide another update within 24 hours.
monitoring
We have identified the root cause and deployed a fix. We will continue to monitor the behavior through the weekend to ensure no further occurrences appear.
identified
We are continuing mitigation efforts for the intermittent issues with the Management API.
identified
Cause isolation is continuing. We are doing work to ensure the accuracy of the understood cause in order to have confidence in the mitigation method under consideration.
identified
We've isolated the cause of the network issues with the Management API and we are working on a fix.
identified
We have been alerted that our Management API is experiencing performance degradation due to intermittent network issues. Users who experience the problem are encouraged to log out and log back in to the dashboard as that has cleared the issue in many cases. Additionally, users can retry failed actions as needed. We are actively investigating a persistent fix.
