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.
July 2026
DNS creation delays
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The upstream DNS provider has implemented a fix and is monitoring the results. We are seeing signs of recovery; we will continue to monitor the situation and will provide further updates as more information becomes available.
identified
We have identified that the issue is with an upstream DNS provider, causing DNS creation delays for newly created, unpaused, or updated databases. Our team is actively monitoring the situation and will provide further updates as more information becomes available.
investigating
We're investigating issues updating DNS records for newly created, unpaused, or updated databases.
Log Ingestion Issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Log ingestion has been restored, and new logs are now appearing as expected. We will continue monitoring to ensure the issue is fully resolved.
identified
We have identified the cause of the issue and are working to restore normal log ingestion. Customers may continue to experience delays in new logs appearing.
investigating
We are experiencing a problem with log ingestion. Customers may experience a lack of new logs being visible from their projects. We are investigating.
Management API Performance Degradation.
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The intermittent networking issues have subsided. Management-api is operating normally now. We will continue to monitor for abnormal behavior.
investigating
We are continuing to investigate the issue. We will provide further updates as progress is made.
investigating
We have identified some anomalies that appear correlated to this issue and we are continuing to investigate.
investigating
We are continuing to investigate the issue.
investigating
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. We are actively investigating a persistent fix.
Issues with Edge Function Deployment
majorSource not attested
Last archived state: resolved
View archived record details
identified
We are working on a permanent fix for issue affecting bulk Function deployments.
In parallel, we are manually assisting customers who have reported the issue through support tickets.
monitoring
Our fix has completed rollout and we are monitoring for full resolution.
identified
The issue has been identified and a fix is being implemented.
investigating
We continue to investigate the root cause of this issue. Some deployment operations have recovered, but we are still investigating reports of failures affecting bulk deployments and updates to existing Edge Functions.
investigating
We are still identifying the root cause of the issue; however, if you are experiencing issues with your Edge Functions, redeployment should resolve that issue. We apologize for any inconvenience.
investigating
We are continuing to investigate this issue.
investigating
Per-function deployment appears to be working successfully. However, bulk function deployments with the `supabase functions deploy` command appear to still be experiencing issues. Additionally, we are aware of reports of issues updating existing function deployments. We are continuing to investigate these issues.
investigating
We have determined and rolled back the change that led to this issue. Users who were experiencing issues with deployments should now be able to deploy successfully.
investigating
Only a subset of users appear to be impacted by the issue with Edge Function deployments. We are investigating the root cause.
investigating
We are aware of some users experiencing issues with Edge Function deployments.
SSO login failures in us-east-1
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have rolled out a fix for the SSO login failures affecting the us-east-1 region. We are monitoring the results and will continue to observe the service to ensure stability before resolving the incident.
identified
We have identified the cause of the SSO login failures affecting the us-east-1 region and are working to implement a fix. We will continue to provide updates as progress is made.
investigating
We are investigating an issue causing SSO login failures in the us-east-1 region. Our team is actively investigating the cause and will provide updates as more information becomes available.
Documents Search Unavailable
minorSource not attested
Last archived state: resolved
View archived record details
identified
We noticed the search function for our documentation was not available as it should be. We're making the necessary updates to fix that problem.
Delays in creation of DNS records
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
All failed DNS creation has been backfilled, and customers should no longer see missing DNS records in their projects. DNS record creation and latency have returned to normal levels. We will continue to monitor before resolving this incident.
identified
We have identified and mitigated the issue that was blocking DNS updates. DNS record creation is succeeding, and latency has returned to normal levels. A subset of projects that encountered provisioning failures during the incident will require DNS records to be backfilled, and we are actively remediating these affected projects.
identified
We have identified the cause of delays in DNS records creation and are actively working on a fix. We will continue to provide updates as things progress.
investigating
We are investigating failures in provisioning DNS records for projects, there may be delays in creation of DNS records for new or unpaused projects.
Project Resize Problems in US-West-2
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have a mitigation in place for resizing issues for projects in us-west-2. We will be monitoring going forward. If your project is in us-west-2, and you experience issues resizing going forward, please open a support ticket so we can directly assist you.
identified
We have identified the cause of the resize issues and are evaluating options for mitigating the problem.
investigating
We are continuing to investigate this issue.
investigating
We have noticed an issue with project resizing in us-west-2 and are investigating.
Authentication issues for some projects
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Authentication has returned to normal.
identified
We have implemented a fix to the authentication issue and are monitoring for recovery.
investigating
Some projects are experiencing authentication issues. We are actively investigating.
Log Ingestion Problems
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor log ingestion to ensure it remains stable.
monitoring
We have implemented a fix, and log ingestion has returned to normal. We will continue to monitor this issue to ensure it stays stable.
identified
We have identified the issue and are working to re-enable the ingestion of logs.
investigating
We are experiencing a problem with log ingestion. Customers may experience a lack of new logs being visible from their projects. We are investigating.
