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.
April 2026
Some projects unavailable across multiple regions
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We believe all users affected by this particular issue have been resolved. The team is going to keep an eye on these error rates to ensure we catch any that didn't originally appear, or that no new issues arise.
We appreciate your patience as we worked through this issue.
identified
The team is continuing their mitigation efforts. We've fixed and restarted most of the affected projects. We're continuously looking for any others that are affected so we can be sure to get them all fixed.
identified
The team is still working to bring these back online, and have a fix under way.
Many users can also resolve this on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time. But for those who are still seeing issues after a restart, we will be pushing a fix soon.
identified
We have identified this issue across multiple regions, not just eu-west-3 as originally suspected. We are expanding the scope of efforts to bring affected projects back online.
Users can also resolve this, in most cases, on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time.
identified
The team is continuing to work through affected projects; however, a project restart is also effective. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time.
identified
We are seeing an increase in projects unavailable in eu-west-3 following an upstream issue with EC2 instances in the region. The team is working on restoring access to these projects
Some Projects Unreachable following Project Restart
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been rolled out, and we are monitoring for continued stability. Any remaining impacted projects are being manually patched.
identified
The permanent fix has now been rolled out across the fleet. We are continuing to manually patch any remaining impacted projects to restore service.
identified
We’ve identified additional impacted projects and are currently working to manually patch and restore them.
We are also continuing to roll out a fix across the fleet to prevent further impact.
monitoring
All impacted projects with open support tickets have now been manually patched and restored.
We are currently rolling out a fix across the fleet to prevent further impact.
We will continue to monitor progress and provide updates.
identified
Our team is actively working on a fix and is manually patching impacted projects to restore service as quickly as possible.
If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved.
identified
We’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script.
This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully.
This can result in projects remaining offline.
We are working on a fix to restore service.
If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved.
identified
We’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script.
This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully.
This can result in projects remaining offline. We are working on a fix to restore service.
Increased errors in project creation and configuration changes in US-East-2 and AP-Northeast-1
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Projects have recovered and capacity has been restored. All previously affected regions have been re-enabled, and we will continue to monitor to ensure stability.
identified
Capacity has been freed, and the regions have been re-enabled. The team is currently working on resolving any failed project starts, resizes, restarts, or other configuration changes during this event.
identified
US-East-2 and AP-Northeast-1 have been disabled for project creation and configuration change actions, and the team is currently working to free additional capacity in these regions.
identified
We are seeing new project creation, resize requests, and project restart failures due to capacity issues in us-east-1. We are disabling project creation, project resize actions, and project restarts in these regions.
We have already reached out to our provider for additional capacity, and will update here as we have additional information.
Newly created projects may be unreachable
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented, and we are seeing improvements in DNS resolution.
We’re closely monitoring to ensure the issue is fully resolved and services remain stable.
identified
We are currently experiencing an issue propagating new DNS records for our zone. We are working closely with our upstream network providers technical team to implement a fix and will share updates as we learn more.
investigating
We are currently investigating reports that newly created projects may be unreachable. Initial findings indicate DNS resolution failures. We will provide an update as soon as more information is available.
Transactional Email Delivery Delays
Source not attested
Last archived state: resolved
View archived record details
monitoring
Customers will continue to see these delayed transactional emails while we clear the backlog. We will provide another update once these queued emails are sent.
monitoring
We have made progress investigating the specific causes of the email spike and are determining appropriate next steps to improve clearance of the backlog.
monitoring
We are experiencing delays in delivery of some of our email to customers related to transactions, including new welcome, oauth-approved, project-shutdown, and payment-failure notifications. This has caused some customers to receive notifications after their issue has been resolved (for example, payment failure notifications after payment has been issued). We are actively monitoring the email delivery queue and expect the delays to be eliminated over time. We will update this status as appropr...
Project creation failures in some APAC regions
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue affecting project creation in some APAC regions.
Users may experience failures when attempting to create new projects in impacted regions.
Existing projects are not impacted.
Our team is actively working to mitigate the issue and restore normal availability.
We will share further updates as more information becomes available.
Logs currently inaccessible via the Dashboard and Log Drains
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
All log sources have been restored and logs should be available to users again now. We are keeping an eye on things to ensure ongoing stability.
identified
The underlying logging platform has stabilized, and some log sources have been restored and are successfully ingesting logs. The team is working to restore the rest of the log sources now.
identified
Users may see errors when attempting to retrieve logs via the Supabase dashboard or may not see new logs arriving via log drains. The team has identified the issue and is working on a fix. Underlying projects are unaffected, this is only affecting the logging service.
Increased error rates for plan upgrades
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been applied, and we are monitoring to ensure stability.
identified
We have identified the cause of increased error rates affecting plan upgrades and are working on a fix.
We will provide further updates as progress is made.
investigating
We are currently investigating increased error rates affecting plan upgrades. Our team is actively working to identify the root cause and restore normal functionality. We will provide updates as more information becomes available.
Degraded logs ingestion
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified the issue and a fix is in place. We will continue to monitor to ensure stability.
investigating
We are seeing degradation of logs and are currently investigating the cause of this issue.
March 2026
Project Creation Degradation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Project creation has returned to normal. We continue to actively monitor and operate our platform for stability and consistency.
identified
We have experienced problems with project creation, the issue has been identified and mitigation steps have been implemented.
