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
The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.
identified
A fix has been developed and we are going through the review and implementation process.
identified
We have identified the issue with the upgrade. To prevent issues, we have suspended the ability to upgrade projects while we resolve this issue. The problem is limited to upgrades from earlier versions of PG17 to the most recent release. We are working on a fix.
investigating
We have observed failures in attempted upgrades to 17.11.0.003. We are investigating.
Increased errors on management api leading to project operation failures
We have identified a rollout causing error increase on management api dependant services, which is causing project operation failures and FGA Authentication errors across multiple functions.
We have implementing a fix and observing recovery. Our teams are continuing to monitor for full resolution.
investigating
We are continuing to investigate this issue.
investigating
We are investigating an increase in errors on project update flows including creation, pausing/unpausing and upgrading across multiple regions.
A fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully resolving this incident.
identified
While we have observed significant improvement in rates of high latency, we note that some users are still experiencing issues during peak Eastern US business hours. We continue to work with our networking partners to isolate and resolve any lingering sources of high latency. We recognize that this is a longstanding issue and appreciate the patience of affected customers. We will continue to share additional updates here as soon as they are available.
identified
Our networking partners have implemented a mitigation to the latency issue at the problematic PoP in the Eastern US, and we have since observed significant improvement in rates of high latency across the region. We are continuing to work with those partners to isolate any additional root causes of latency and improve the reliability of our networking infrastructure across the region.
identified
We are seeing signs of improvement and are continuing to work alongside our networking partners towards a resolution.
We will provide another update as more information becomes available.
identified
We're continuing to coordinate with our networking partners to deliver a permanent resolution.
We will provide updates as soon as they're available.
identified
We are working with our networking partners on a permanent fix.
While we do not have an estimated resolution time, we will share updates here as they become available.
identified
A mitigation for this issue was applied earlier today, but we do not have sufficient evidence to conclude that the mitigation resulted in improvement to this eastern US latency issue. We have tied the issue to a particular PoP, and we are continuing to work with our networking partners to bring this issue to a final resolution. We will provide another update within 4 hours, if not before. We appreciate your patience.
identified
We are continuing our work to fix this latency issue, which has been observed to impact clients connecting to Supabase Projects from the eastern United States. These clients may include servers and serverless functions located in that geographical region, regardless of the region in which the Project is hosted.
identified
We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks.
We are actively working on a fix. We will provide updates as the fix is implemented.
We are continuing to monitor to ensure ongoing stability.
identified
The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.
identified
Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon.
This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available.
identified
All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.
identified
We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.
investigating
We are investigating project lifecycle operation issues in eu-west-1.
We have applied a fix, and administrative operations in the Supabase Dashboard are now completing as expected.
We are monitoring the results to ensure the issue is fully resolved.
identified
We have identified the issue causing some users to encounter permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard.
We are working on a fix and will provide another update once it has been implemented.
investigating
We are investigating reports of users encountering permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard.
This may prevent some users from managing their projects through the Dashboard.
We are working to identify the cause and will provide further updates as they become available.
We are no longer seeing rate limiting issues affecting Supabase CLI CI workflows. We're continuing to monitor the service for stability while we roll out a fallback patch to improve resilience and help prevent the issue from recurring.
identified
We've identified the cause and are working on a fix.
A fix has been implemented for the affected tenants and we are monitoring the results. We will continue to monitor the situation and will provide further updates as more information becomes available.
investigating
We have identified an issue with Storage for projects are restoring from backups. Users may experience increased 500 errors.
We are working to identify the root cause and will notify for any progress as soon as we have an update
Increased error rate in project creation and project restore
A fix has been implemented and we are monitoring the results.
identified
We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.
investigating
We are currently investigating this issue
Supavisor connection disruptions in EU West 1 (Ireland)
The affected Supavisor node has been restarted, and error rates have returned to normal levels.
We’ll continue to monitor the service to ensure stability.
investigating
Some projects in the EU West 1 (Ireland) region may experience disruptions to Supavisor connections.
Our team is aware of the issue and actively working on a resolution.
We’ll share further updates as they become available.
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.
