New Multi-region uptime checks and custom-domain status pages

Supabase Outage History

Daily provider-status observations and published incident history for Supabase.

Operational

Supabase is operational. Verified . Official provider source.

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

Jul 15Oct 12

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 14 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

October 2026
Upgrade Issues
minor Observed active window 2h 56m

View incident details and source

Started:

monitoring
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
minor Observed active window 1h 11m

View incident details and source

Started:

Management API
monitoring
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.
September 2026
Intermittent latency in Eastern US
minor Observed active window 163h 53m

View incident details and source

Started:

API Gateway
monitoring
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.
Log Ingestion Degradation
minor Observed active window 52m

View incident details and source

Started:

monitoring
Log ingestion has recovered. We are monitoring for continued stability.
identified
The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.
investigating
Log ingestion is experiencing some delays. Ingestion will be retried by clients.
Project Lifecycle Issues in eu-west-1
major Observed active window 2h 3m

View incident details and source

Started:

Database Management API eu-west-1
monitoring
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.
Permission errors in the Supabase Dashboard
critical Observed active window 1h 12m

View incident details and source

Started:

Dashboard
monitoring
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.
Supabase CLI CI workflow failures
minor Observed active window 1h 46m

View incident details and source

Started:

monitoring
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.
investigating
We're seeing rate limiting issues causing Supabase CLI CI workflow failures
Storage search failing for restored projects
minor Observed active window 24h 33m

View incident details and source

Started:

Storage
monitoring
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
major Observed active window 1h 28m

View incident details and source

Started:

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-1 eu-west-2 eu-west-3 sa-east-1 us-east-1 us-east-2 us-west-1 us-west-2
monitoring
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)
minor Observed active window 1h 30m

View incident details and source

Started:

Connection Pooler
monitoring
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.

March 2026
Degraded Log Ingestion
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal.
identified
We continue to increase capacity in targeted areas to mitigate log ingestion degradation. It will take some time for the ingestion backlog to be eliminated.
identified
We have implemented increase capacity and logs are returning to normal. It will take some time for the ingestion backlog to be eliminated. Some services, such as realtime, storage, and api-gateway, will have lost logs during the ingestion incident.
identified
We have identified the issue with log ingestion. We are testing mitigation options, including bringing up additional capacity. We will continue to update this page with our progress.
investigating
We are investigating a problem with log ingestion. Users may experience delay in current log data.
Realtime services unavailable
major Source not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been implemented and we’re monitoring to ensure stability.
identified
We appreciate your patience as we continue to work on a fix. We will provide updates as they become available.
identified
We are working on a fix and we’ll continue to provide updates as progress is made.
identified
We've identified the issue and are currently working on a fix, we will provide an update on our progress soon.
investigating
We're still investigating network connectivity issues with Realtime.
investigating
We are investigating network connectivity issues with Realtime.”
Branching access issues
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been implemented and branching access has returned to normal.
identified
We are aware of an issue affecting users creating/updating branches. A permission error in our branching workflow is causing failures for all branches. We have identified the root cause and a fix is being deployed. We will provide an update once resolved.
Degraded Logging Ingestion impacting all regions
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented. The system is now operating normally, and we will continue to monitor.
identified
The cause of the issue has been identified. Our engineering team is working on a fix.
investigating
We are currently investigating an issue affecting Supabase Logs, resulting in partial log ingestion for some services. Users may experience delays or errors when accessing logs. In some cases, logs may be partially ingested or not ingested at all. Projects remain fully functional. This issue is limited to logging only. Our team is actively working to identify the root cause and restore normal performance as quickly as possible. We will provide further updates as more information becomes ava...
Elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We carried out a controlled redeployment of the affected services to restore stability. The system is now operating normally, and we will continue to monitor.
investigating
We are currently investigating elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region
Project creation failures across multiple regions
major Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue and a fix is underway.
investigating
We are currently investigating project creation failures across multiple regions.
Elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region
minor Source not attested
Last archived state: resolved
View archived record details
identified
The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix.
investigating
We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. While we are still observing a higher-than-normal level of errors, initial findings indicate that the overall impact is lower than first expected. Many affected requests are succeeding upon retry. Our team is actively working to determine the root cause and will provide further updates as more information becomes available.
investigating
We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. Newly created projects may still experience issues connecting to storage, while existing projects remain unaffected at this time. Our team is actively working to determine the root cause and assess the full impact. We will provide further updates as more information becomes available.
investigating
We are currently investigating elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. Newly created projects may experience issues connecting to storage, while existing projects remain unaffected at this time. We are actively working to understand the full scope of the impact and will provide further updates as more information becomes available.
Issues propagating Postgres configuration updates
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring.
identified
We have identified the root cause and are currently working on a fix.
investigating
Some custom Postgres configurations applied through the Supabase CLI are not currently taking effect for projects running Postgres version 17.6.1.084. Projects that do not use CLI-managed Postgres configurations, or that are running earlier Postgres versions, are not affected.
Increased error rate related to Connection Pooler in ap-northeast-2 (South Korea)
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and error rates have reduced. Our team is actively monitoring the system to ensure stability.
investigating
We continue to investigate increased error rates relating to the connection pooler in ap-northeast-2 (South Korea) We will provide further updates as information becomes available.
investigating
We are currently investigating increased error rates relating to the connection pooler in ap-northeast-2 (South Korea) We will provide further updates as information becomes available.
Degraded Logging Ingestion impacting all regions
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and log ingestion is now stabilising. We are seeing recovery across the affected services. Our team is actively monitoring the system to ensure ingestion fully returns to normal.
investigating
We are currently investigating an issue affecting Supabase Logs that is causing partial log ingestion for some services. Users may experience delays or errors when accessing logs related to Realtime, Storage, or Edge Functions logs. The logs for these services may only be partially ingested. The services remain fully functional, this is only impacting logs. Postgres Logs are not impacted. Our team is actively working to identify the root cause and restore normal performance as quickly as...
Get alerts for Supabase Subscribe to the provider incident feed Browse all services