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.
May 2026
Network restrictions preventing read replica communication
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have merged the fix and are monitoring for stability.
identified
We have developed a fix and it is currently being validated. We will provide more updates soon.
identified
Our team continues to work on implementing a fix for the issue. We will provide additional updates as progress is made.
identified
Our team continues to work on implementing a fix for the issue. We are continuing to monitor the impact and will provide additional updates as progress is made.
identified
We have identified the cause of the issue impacting read replica communication for projects. Our team is actively working on a fix and continuing to assess the impact to affected projects.
investigating
We are reviewing the impact of this issue, which is limited to projects with read replicas and network restrictions. We continue to both investigate mitigation options for the issue and identify projects that may be impacted.
investigating
Network restrictions are preventing read replicas from communicating with their primaries for a limited number of customer projects. We are actively investigating this issue.
Paused Projects Showing Incorrect Resume Deadline
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
This change has been reverted. We are monitoring to ensure things remain stable.
identified
The revert of the change is in process.
identified
We’ve isolated the cause of the issue to a recent change and are working on reverting it now.
investigating
We are currently investigating a UI issue affecting paused projects, where an incorrect resume deadline is displayed in the dashboard.
The message incorrectly states that projects can be resumed within 90 days while also displaying today’s date as the expiry date.
For example:
“All data, including backups and storage objects, remains safe. You can resume this project from the dashboard within 90 days (until 20 May 2026). After that, this project will not be resumable, but data will still...
Log ingestion issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Logging systems have returned to normal operation.
During the incident, some logs may have been delayed or unavailable. While certain upstream log sources may retry delivery automatically, we cannot guarantee recovery of all missing logs generated during the affected time period.
We will continue monitoring closely to ensure ongoing stability.
investigating
Customers may experience delayed log ingestion or periods where logs are unavailable. We will provide updates while we work to resolve the issue.
Auth Service Update
Source not attested
Last archived state: resolved
View archived record details
monitoring
The update has been implemented. Service changes can be made. We will monitor the effect for the next 30 minutes to ensure stability.
identified
We need to implement a time-sensitive update to our Auth service. Please do not make any changes to your Auth service until we have completed this update.
Access Issues From Some Providers in Brazil
Source not attested
Last archived state: resolved
View archived record details
monitoring
The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal. We will monitor this for continued functionality.
monitoring
We continue to work with the relevant provider and have seen improvements. We are monitoring the progress that has been made to ensure it continues.
identified
We are engaged with senior networking team members at the impacted provider. They are actively investigating the domain name resolution issues we have reported. If you are continuing to experience .co name resolution issues in Brazil, please update your ticket or open a new ticket to let us know so we can add that information to the investigation.
identified
We continue to work with the service provider to resolve the residual access issues. We have scheduled direct consultations with the provider to attempt to resolve the issue.
identified
We are continuing to contact the ISP in Brazil to work through this issue: however they have remained unresponsive to outreach. We are exploring other options to get in touch with them.
Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share.
identified
We are continuing to contact the ISP in Brazil to work through this issue. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share.
investigating
We have made contact with the ISP in Brazil and are working through their support process for this issue. Customers may be able to bypass the problem by using a VPN or alternative network while we work towards resolution.
investigating
We have isolated the issue to a specific Internet provider in Brazil and are working to contact that provider to resolve the issue. We will update the statuspage when we have more information to share.
investigating
We are investigating reports of some access issues to Supabase IP addresses from a network provider in Brazil.
Reports of issues connecting to API Endpoints
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating reports of connectivity issues to project API endpoints.
Edge Traffic Issues
minorSource not attested
Last archived state: resolved
View archived record details
identified
Our investigation has identified traffic loss along a specific network path associated with a VPN exit point located in Western Europe.
Some customers are experiencing connectivity issues that impact a subset of users connecting through certain VPN providers, including Mullvad.
Customers impacted while using Mullvad can contact Mullvad support directly to help raise visibility into the issue from their side.
investigating
We are continuing to actively investigate the connectivity issues impacting access to Supabase APIs for some users.
Our team remains engaged in identifying the underlying cause and validating the scope of impact. We will continue to provide updates as our investigation progresses.
investigating
We are continuing to investigate connectivity issues impacting access to Supabase APIs, which may result in connection timeout errors or rejected connections for some users.
At this time, we have narrowed the issue down to traffic originating from at least one VPN provider (Mullvad VPN). However, we cannot yet confirm whether additional VPN providers may also be impacted.
We are actively working to identify the root cause and will continue to provide updates as we learn more.
investigating
We've observed traffic from upstream providers of a VPN provider is no longer reaching our servers. We're investigating the cause and will keep you updated.
Customer Projects Experiencing Upgrade Issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified the root cause and developed a fix, which has been applied in production.
Projects which have failed to upgrade will be automatically recovered and returned to ACTIVE_HEALTHY without manual intervention.
Any future upgrades should complete successfully.
We are continuing to monitor recovery and system stability closely.
identified
We are continuing to investigate issues impacting project upgrades.
We have observed that the majority of affected projects are successfully returning to a healthy state on their previous PostgreSQL version following failed upgrade attempts. Our engineering team is actively working to manually restore the remaining projects that are still stuck during the upgrade process.
As a precaution, we recommend that customers do not attempt to upgrade their projects until this incident has been fully r...
identified
We are continuing to work on a fix for this issue.
identified
Our engineering team are investigating issues with customer projects being stuck when upgrading Postgres version.
We advise that you do not upgrade your project until the incident is resolved.
Network connectivity in us-east-1-az4
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our infrastructure provider has resolved the underlying incident, and impacted services have recovered.
We have completed recovery efforts for affected projects, re-enabled project creation, pausing, and compute resizes in the us-east-1 region, and are now monitoring the platform to ensure continued stability.
identified
Our infrastructure provider has resolved the underlying incident, and the majority of impacted projects have now recovered.
Our team is currently working through the remaining projects that did not automatically self-heal during recovery and is actively restoring them manually where needed.
We have also re-enabled project creation, pausing, and compute resizes in the us-east-1 region.
We are continuing to monitor platform stability closely and will provide additional updates as recovery progr...
identified
Our team continues to make progress restoring impacted projects safely and as quickly as possible.
To support recovery efforts, project pausing and new project creation in the us-east-1-a4 region continue to be disabled.
While recovery efforts are moving forward, full resolution is still expected to take several more hours based on the latest guidance from our infrastructure provider.
We understand the impact this is having and appreciate your continued patience. We’ll continue to share upd...
identified
Our team continues to make progress restoring impacted projects safely and as quickly as possible.
To support recovery efforts, project pausing and new project creation in the us-east-1-a4 region continue to be disabled.
While recovery efforts are moving forward, full resolution is still expected to take several more hours based on the latest guidance from our infrastructure provider.
We understand the impact this is having and appreciate your continued patience. We’ll continue to share upd...
identified
Our team is actively working to bring impacted projects back online as quickly and safely as possible.
While we are seeing progress, full recovery may still take several hours based on the latest guidance from our infrastructure provider.
We appreciate your patience and will continue to share updates as more information becomes available.
identified
Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
identified
Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
identified
Affected projects are continuing to recover. We are monitoring the recovery of the AZ and will provide regular updates until full recovery.
identified
We're starting to see a number of affected projects starting to recover. We're still working with our upstream providers on a full recovery of all affected projects.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We've disabled pausing projects in us-east-1. We recommend not changing project configurations at this time. Users cannot access their databases or run any authentication-dependent services. We are continuing to monitor this situation with our upstream provider.
identified
We have disabled project creation in us-east-1. We will provide another update in an hour, if not sooner.
identified
We are waiting on a resolution from our upstream provider. We will provide an update in an hour.
identified
We have identified the root cause of the connection issues as an outage with an upstream provider affecting a single availability zone (us-east-1a). All affected projects are located in this zone.
investigating
Increased connection times for Supavisor since about 00:10 UTC is affecting a limited number of projects in us-east-1
April 2026
403 errors for PostgREST requests
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The exceptions fix has been rolled out, and we are monitoring for continued stability.
identified
We are continuing to work on a fix. We’ll share further updates as progress is made.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and we are working on a fix.
investigating
We are investigating 403 errors for PostgREST requests across multiple regions.
