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
Project Actions Failing Across Multiple Regions
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality.
identified
We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results.
investigating
We are testing mitigation options to attempt to restore project action performance.
investigating
We have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel.
investigating
Project actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance.
investigating
Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.
S3 endpoints for keys with special characters broken
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress
identified
A likely mitigation has been identified and we are discussing the proper implementation method.
identified
We have identified an issue where S3 endpoints for keys with special characters will be broken. We are actively investigating the correct mitigation for this issue.
Projects in stuck state in EU-CENTRAL-1 (Frankfurt)
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
All impacted projects have now been successfully restarted, and functionality has been restored.
We are moving this incident to Monitoring for an additional hour while we continue to ensure stability.
If you believe your project in eu-central-1 (Frankfurt) is still impacted by this issue, please open a support ticket and we'll work with you directly to investigate.
identified
The majority of impacted projects have now been recovered, and functionality has been restored for most customers.
Our team continues to work through the remaining affected projects individually to restore normal functionality as quickly as possible.
We will continue to provide updates as this work progresses.
identified
The majority of impacted projects have now been recovered, and functionality has been restored for most customers.
Our team continues to work through the remaining affected projects individually to restore normal functionality as quickly as possible.
We will continue to provide updates as this work progresses.
identified
We are continuing to work on a fix for this issue.
identified
Our infrastructure provider experienced a connectivity issue in the EU-CENTRAL-1 (Frankfurt) Region, between 4:11 PM PDT and 6:24 PM PDT, which has now been resolved.
As a result of this incident, a number of Supabase projects were left in a stuck state.
Our team is actively working through the list of impacted projects to restore normal functionality as quickly as possible.
We will continue to provide updates as restoration work progresses.
Errors configuring authentication providers
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been deployed for the issue that affects configuring Authentication Providers. We are monitoring the results to confirm the issue has been fully resolved.
identified
We have identified the issue and are actively working on a fix. We will share another update as soon as we have more information.
investigating
We are currently investigating an issue affecting the ability to view and manage authentication providers in the Supabase dashboard.
Degraded log ingestion
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented a fix for the issue affecting log visibility that began at approximately 22:15 UTC. Log ingestion has returned to normal. We are monitoring the system to ensure the issue is fully resolved.
If you continue to experience missing or delayed logs from the affected period, please contact Support for assistance.
identified
We've identified the issue and are implementing a fix.
If you need access to logs from the affected period (starting at approximately 22:15 UTC), please contact Support and we will work with you to retrieve them.
investigating
We continue to investigate an issue affecting log visibility that began at approximately 22:15 UTC. During this time, logs may be delayed or unavailable.
Our team continues to investigate the underlying cause and will provide another update as more information becomes available.
If you need access to logs from the affected period, please contact Support and we will work with you to retrieve them.
investigating
We are continuing to investigate the issue affecting log ingestion across all regions. Logs may be delayed or unavailable. We will provide another update as soon as more information becomes available.
investigating
We are continuing to investigate the issue affecting log ingestion across all regions. Logs may be delayed or unavailable. We will provide another update as soon as more information becomes available.
investigating
We are currently investigating an issue affecting log ingestion across all regions. During this time, some logs may be delayed or unavailable.
Elevated JWT authorization errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A rollback mitigation implemented by our team has addressed the problem. Edge functions have returned to normal. We will continue to monitor performance.
identified
We have identified likely reasons for the problem and are investigating options for resolution. We advise all customers to ensure they are using valid JWT keys with their projects.
investigating
We are aware of reports of elevated legacy JWT authorization errors on edge functions in some regions
Project creation delays in AP regions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Recovery has continued and project creation in the relevant region has returned to normal. We will continue to monitor this for another 30 minutes.
identified
Project creation is recovering. We are actively tracking recovery.
identified
We have identified options for mitigation and are discussing the best implementation methods for them.
identified
We continue our investigation into how to mitigate the project creation delays. We are examining relevant data paths in detail.
identified
We have identified the cause of the creation delays and are actively working to address the problem.
investigating
We are aware of project creation taking longer than normal in AP regions. A retry should enable completion of creation for those impacted. NOTE: This incident is not related to the ongoing capacity issues incident we are monitoring.
Endpoints in Americas regions returning 500 Internal server error
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been applied and there are improvements to the error rates. We are continuing to work on ensuring the underlying issue does not recur.
identified
We have identified the cause of the 500 errors and are implementing a fix.
investigating
The scope of the errors is across regions in the Americas. We are narrowing down the likely causal chains.
investigating
The 500 errors are limited to us-east-1, we are actively exploring causes.
investigating
Multiple endpoints are returning 500 Internal server errors across our platform. We are investigating what has caused these errors.
Degraded project creation success rates in the ca-central-1 region
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have restored project creation startup time in ca-central-1 and are monitoring the situation for full recovery.
identified
We are redirecting project creation to more healthy regions and working to continue to increase the success rate in ca-central-1.
A longer startup time is expected while project creation is recovering in ca-central-1.
identified
We are continuing to work on a fix for the issue and will provide another update as soon as we have more information to share.
identified
We have identified the root cause and are working on a fix.
investigating
We are seeing degraded project creation success rates in the ca-central-1 region. We are currently investigating the issue, and will provide an update soon.
Errors when attempting to view advisor results in the Supabase dashboard
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've deployed the fix and are now monitoring the issue.
identified
We continue to work on a fix for advisor results in the Dashboard. Affected users may be unable to run Performance Advisors and may see an error when attempting to view advisor results in the Dashboard.
identified
We are investigating an issue affecting the Performance Advisors feature for some projects.
Affected users may be unable to run Performance Advisors and may see an error when attempting to view advisor results in the Dashboard.
Our team has identified the cause and is working to implement a fix.
We will provide another update as soon as more information becomes available.
