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.

July 2026
Project Actions Failing Across Multiple Regions
major Source 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
minor Source 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)
major Source 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
minor Source 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
minor Source 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
minor Source 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
minor Source 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
major Source 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
minor Source 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
minor Source 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.
Get alerts for Supabase Subscribe to the provider incident feed Browse all services