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
Delays in newly created project setup
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Provisioning times and project lifecycle operations have returned normal. We will continue to monitor.
identified
We are currently seeing delays affecting the setup of Realtime, Storage, and shared pooler services for newly created projects.
Customers may experience longer than expected provisioning times after creating a new project, and some project lifecycle operations may also be delayed while setup completes.
Our team is has identified the issue and are working to restore normal provisioning times. We will provide another update as soon as we have more information.
Issues with Restore to New Project
Source not attested
Last archived state: resolved
View archived record details
identified
We have identified an issue with the Restore to New Project beta feature and we are implementing a fix. The Restore to New Project beta feature will be temporarily unavailable while we fix this issue. We will update this page when the fix has been rolled out.
Functions management API is returning 500s for multiple function operations
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented a fix, and error rates have returned to expected levels.
We are continuing to monitor the platform closely to ensure the issue is fully resolved.
identified
The team has identified the root cause of the issue and is currently rolling out a fix across the platform.
We will continue to monitor the rollout and provide another update once it has been completed.
investigating
We are currently investigating an issue affecting the Edge Function API requests.
Our team is working on a fix, and we will provide another update as soon as more information becomes available.
June 2026
Connection issues in Supavisor us-east-1 cluster
Source not attested
Last archived state: resolved
View archived record details
monitoring
We believe the issue has resolved. We are monitoring for any recurrence.
investigating
We have detected increased rates of connection issues in a us-east-1 Supavisor cluster starting at 14:10 UTC. Our team is currently investigating.
Upgrade Failures
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented all necessary mitigations and the project upgrade rates have returned to normal across the fleet. We will continue to monitor these flows for any irregularities or recurring degradation. If you are still experiencing delayed or blocked upgrades on your Project, please contact Support.
identified
We are starting to notice improvements as a result of our mitigation efforts, and expect that project upgrades should start to become less delayed. We’ll continue monitoring and will update as we observe improvements across the fleet.
identified
We are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems.
identified
We are implementing operational mitigations to try to improve upgrade performance.
identified
We are continuing to work through a variety of options for improving upgrade performance. This includes working with our upstream provider and adjusting operational parameters.
identified
We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades.
identified
The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources.
investigating
Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays.
investigating
We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps.
Elevated errors on Postgres change subscriptions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have applied a fix and are monitoring the results to ensure the issue is fully resolved.
identified
We have identified the cause of the elevated errors affecting Postgres change subscriptions and are actively working on a fix. We will provide another update as soon as we have additional information or progress to share.
investigating
We are investigating an issue causing elevated errors for some customers using Postgres change subscriptions. Our team has identified the affected component and is actively working to determine the root cause and implement a fix. We will provide another update as soon as more information is available.
Degraded performance of the Shared Pooler cluster in ap-southeast-1
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are aware of a period of degraded performance of the Shared Pooler cluster in ap-southeast-1. Affected projects experienced increased ECHECKOUTTIMEOUT errors when running queries.
The window of the incident was between 14:48 to 15:25 UTC. The issue appears to be resolved. We are investigating the cause of this incident and will continue monitoring the cluster.
Project create and unpause errors in eu-west-1
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Key updates and other mitigations have been fully deployed and project creation and unpause functionality is returning to normal. We will continue to monitor this region for stability for the next 30 minutes.
identified
During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect.
identified
Multiple mitigations have been deployed and project create performance is improving.
identified
We have identified the issue is related to keys and are preparing a mitigation.
investigating
We are investigating errors in creating and unpausing projects in the eu-west-1 region.
Increased latency for Management API requests
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Latency has returned to normal levels, and we are seeing greatly improved stability across the management API. We are monitoring for any further issues.
identified
We are seeing increased latency on management API requests, which results in slower-than-usual Dashboard performance, project creation and configuration changes may also be delayed. This is primarily affecting US-East-1; however, we are seeing additional latency in other regions as well.
The team has identified the issue and is working on resolution.
Failed to apply network restrictions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have now deployed a fix for this issue across all regions, and we believe this issue to be resolved. We are continuing to monitor for any remaining issues. Please contact Support if you are experiencing any problems with your network restrictions list.
monitoring
We have started deploying a fix for the issue and are validating the results as the rollout progresses. We will continue to provide updates as we move toward full resolution.
identified
We have identified the root cause of the issue and are actively working on implementing a fix.
investigating
We are aware of some users reporting issues adding new entries to their network restriction lists, and we are currently investigating this issue.
