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
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.
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.
