Live status · checked every 15 minutes
Is Supabase down right now?
Supabase is a Postgres backend with auth, storage, realtime and edge functions.
Live reader reports
Is Supabase down for you?
Tap what's not working, or tell us it works. Reports are anonymous, one per visitor.
No reports in the last 24 hours. Be the first to tell other readers what you're seeing.
Supabase not working for you?
- Check your internet connection and any VPN or corporate proxy.
- Sign out and back in, or try a private browser window.
- Check the specific feature you use on the official status page: one part can be down while the rest works.
- Retry failed API calls and jobs with backoff.
Supabase outage history
Last 30 daysFixed Edge Function Issues in ap-northeast-1
-
The mitigation has successfully restored Edge Functions to normal operation in ap-northeast-1. This issue is resolved.
-
The mitigations have returned functions response to normal. We will continue to monitor for stability.
-
We have implemented a mitigation to stabilize the functions service.
-
We have identified an increase in edge function errors in ap-northeast-1, we continue to investigate.
-
We experienced an issue with edge functions in ap-northeast-1 between 20:00 and 20:10 UTC, we are investigating.
Fixed ‘Project not specified’ errors reported for users in ap-northeast-2
-
Projects in ap-northeast-2 have recovered and this issue is now resolved.
-
Between 04:56 UTC - 06:20 UTC projects in ap-northeast-2 encountered 4xx/5xx http errors retrieving project configuration from our upstream network partner with the error: Project not specified. The issue has since recovered and we are working with our network partner on a full review. We will continue to monitor this issue until confirmed resolved.
-
We are investigating reports of users receiving ‘Project not specified’ errors in ap-northeast-2.
Fixed Projects in sa-east-1 experiencing delayed event ingestion
-
This issue is now resolved.
-
The issue has been recovered for projects impacted in sa-east-1. Actual project health or uptime has not been impacted at any time. Users still experiencing an unhealthy event notification on their dashboard can re-start their project to recover. A full fix will be deployed end of today UTC.
-
EC2 scheduled events are timing out for projects in sa-east-1, leading to a subset of projects being reported as unhealthy in the Dashboard. As a workaround, impacted users can re-start their project while we are working on providing a fix.
Fixed Elevated Error rates for All Supabase project APIs
-
This issue has been resolved. All API routes are operating normally, and we are no longer observing elevated error rates.
-
We have isolated the error rates to an individual project with a very unusually high request rate, and we have determined there is no widespread issue as we originally suspected. We will continue to monitor to ensure things remain stable, but all API routes are nominal.
-
We are currently seeing slightly increased error rates for API requests to the Data APIs, Auth, Storage, and other HTTP API routes across all regions The team is currently investigating.
Fixed Database Connection Errors
-
The issue has been resolved, and services across all affected regions have recovered. We are no longer observing elevated connection errors and will close this incident.
-
We are seeing continued improvements across affected regions, and services are recovering. We are moving this incident to monitoring while we continue to verify stability.
-
We have identified the issue and are implementing a fix. We are seeing improvements across affected regions. We will continue to provide further updates as they become available.
-
The impact is not limited to the regions initially identified. Only a subset of projects are affected. Affected projects may continue to experience increased connection errors or database unavailability. We are continuing to investigate and will provide further updates as more information becomes available.
-
We continue to investigate the root cause of this issue and will provide updates as more information becomes available.
-
We have observed increased connection errors, some databases may be unavailable with all services unhealthy.
Fixed Storage request degradation in eu-west-1
-
We have mitigated the issue with the Storage service and we have not observed any further issues during our monitoring period. We consider this incident to be resolved.
-
Between 14:14-14:18 UTC and 14:25-14:29, Storage requests may have been slow or aborted in the eu-west-1 region. This issue has been resolved and we do not expect recurrence. We are monitoring the region.
Fixed Project Lifecycle Issues in ap-northeast-1
-
All operations have returned to normal and have remained stable.
-
We are seeing recovery of project operations. We will continue to monitor to ensure all project lifecycle functions stabilize.
-
Our upstream provider is reporting improvements to project lifecycle actions. We are internally validating the recovery of our systems. We will re-enable functionality after we have confirmed recovery.
-
The issue has been identified by our upstream provider and is being addressed.
-
Project lifecycle operations have been impacted by an issue in ap-northeast-1. We are investigating along with our upstream provider.
Fixed Interruption in connections to Supavisor in eu-west-2
-
The interruption to Supavisor connections in eu-west-2 has been resolved. Monitoring has confirmed that systems have recovered and connections are operating normally.
-
We detected an interruption in connections to Supavisor in eu-west-2 between 09:42 and 09:52 GMT which may have affected connections for some users. This has since been resolved and we are monitoring to ensure all systems have fully recovered.
Fixed Increased Errors with Project Lifecycle Operations in US-West-2
-
The upstream provider incident has been resolved, and Project Lifecycle operations in US-West-2 have recovered. All operations are functioning normally, and we are marking this incident as resolved.
-
Our upstream provider has implemented changes, and we are seeing recovery in project creation in US-West-2. We will continue to monitor the recovery of Project Lifecycle operations to ensure stability.
-
We continue to work with our upstream provider as they investigate the ongoing incident affecting US-West-2. There are no additional updates at this time, and Project Lifecycle operations remain impacted. Currently active projects remain unaffected. We will provide another update in 2 hours, or sooner if additional information becomes available.
-
All Project Lifecycle operations are currently impacted by an upstream provider incident affecting EC2 instances in US-West-2. Currently up and active projects are unaffected and remain healthy. New project creation, unpauses, restore actions, project size changes, restarts and other lifecycle operations may encounter errors. We advise against taking these actions in US-West-2 at this time while we work with our provider to resolve this issue.
Fixed Intermittent 502/503 errors for pg_net calls to Edge Functions
-
The issue has been resolved, and pg_net calls to Edge Functions in ap-southeast-1 are now operating normally.
-
We are seeing intermittent 502 and 503 errors affecting Edge Functions requests in ap-southeast-1. We will provide updates and more information becomes available.
Fixed Storage issues in us-east-1 and eu-central-1
-
The incident has been resolved.
-
The planned database capacity increase for Storage in us-east-1 was completed at 08:06 UTC. Some requests to Storage in us-east-1 may have failed briefly while the database switched over during the change. Storage in us east-1 and eu-central-1 is operating normally. We are continuing to monitor Storage error rates.
-
We will be conducting maintenance to address storage service improvements between 0800 and 0900 UTC on 5 November 2026. There may be an interruption of storage services in us-east-1 at some point during that window. The impact will be of a short duration and limited to us-east-1.
-
The cause of the issue has been identified as directly related to load. We will be doing maintenance on our platform to address this issue. As of now, storage response has returned to normal. We will continue to monitor the environment.
-
We are still investigating increased error rates for storage requests, and have expanded the investigation to eu-central-1 as well. The team has identified higher-than-usual load in some areas of the storage infrastructure and is currently working on remediation options.
-
We have identified some customers in us-east-1 are experiencing 5XX errors when interacting with our Storage components. We are investigating.
Fixed Intermittent errors on Supavisor Shared Pooler in us-east-2
-
Errors have subsided and connections are back to normal.
-
Between 2026-11-04 00:02 and 00:50 UTC there were elevated errors on Supavisor Shared Pooler in the us-east-2 region. Errors have subsided and things are back to normal. Example errors were ``` ClientHandler: (ECHECKOUTFAILED) checkout failed due to %{"C" => "08006", "M" => "Failed to connect to database: {:error, :timeout} DbHandler: Connection failed {:error, :timeout} to ~c".......us-east-2.compute.internal" ```
Fixed Management API Postgres config updates overwriting previous updates
-
Connection Logging feature is working fine for all customers now.
-
A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.
-
We have identified the cause and are deploying a fix. The dashboard setting that was temporarily disabled will soon be enabled again.
-
We are actively correcting an issue with the Management API: • Postgres Config changes only save the latest values sent. Past changes are being overwritten For now, we have disabled making certain Postgres config changes on the dashboard until the issue is resolved.
-
We are actively correcting an issue with the Management API: • Postgres Config changes only save the latest values sent, past changes are not being saved For now please refrain from not making any Postgres Config changes via the [Management API](https://supabase.com/docs/reference/api/introduction) or in the [Database Settings Dashboard](https://supabase.com/dashboard/project/\_/database/settings)
Fixed Storage uploads failing in us-east-1
-
Storage uploads have remained stable, and this issue is now resolved.
-
The fix has been implemented, and we are seeing Storage uploads return to normal. We will continue monitoring to ensure stability.
-
We have identified the issue causing Storage uploads to fail and are working on a fix. We will provide more updates as things progress.
-
We are investigating an error with Storage uploads returning 5xx errors for us-east-1 users. We will be confirming more information shortly.
Fixed PG15 -> PG17 Upgrade Failures
-
This issue is now resolved.
-
We are seeing successful upgrades again, and error rates have returned to normal levels. We will continue to monitor to ensure continued stability.
-
We are actively investigating some reports of failed PG15 -> PG17 upgrades. We have identified an error in an AMI release from today and are rolling it back to unblock upgrades.
Fixed Logs degraded in multiple regions
-
We have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC. Service is now operating normally. We apologise for the disruption
-
A fix has been deployed and we are now monitoring the log service. We'll post another update as soon as we have one.
-
We have identified the cause of the Logs degradation and a fix is being prepared. Other services remain unaffected. We'll post another update as soon as we have one.
-
We are currently investigating degraded Logs functionality in multiple regions. Some users may experience delayed, missing, or unavailable logs in the Dashboard and Logs API. Other services, including your database and APIs, are not affected at this time. Our team is actively investigating. We'll post another update as soon as we have one.
Fixed Delayed Log Delivery from 14:10 - 15:30 UTC
-
This issue has been resolved and log delivery is operational again.
-
Between 14:10 - 15:30 UTC we have experienced an issue in delivering logs, leading to a delay of about 7–8 minutes. Most affected events have now been recovered - a small subset of events is still being re-inserted and we will confirm once completed.
Fixed Log Drain Issues
-
This issue is now resolved.
-
The rollback has restored log drains to normal operation. We will monitor for continued functionality.
-
Customers using log drains in some regions may be missing some routed logs for a subset of components. We've rolled back changes and are continuing to investigate.
Fixed Elevated Mgmt API Error Rates in Multiple Regions
-
This issue has been resolved and our response times are back to operational.
-
We have additional mitigations we will be deploying to reinforce the Management API. Updates will be forthcoming if anything changes that could impact customers.
-
We have additional mitigations we will be deploying to reinforce our backplane. We will leave this statuspage up and in Monitoring status until all mitigations are deployed. Updates will be forthcoming if anything changes that could impact customers.
-
The mitigations have managed the demand spike. We are monitoring for continued stability.
-
We have identified the issue as related to the demand on our backplane. We are implementing mitigations to scale and manage that demand.
-
We have noticed issues with requests coming to our API gateway. We are investigating.
Fixed Elevated Mgmt API Error Rates in Multiple Regions
-
Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.
-
A mitigation has been applied. Error rates and latency have returned to normal levels. We’re continuing to monitor to ensure sustained stability before resolving this incident.
-
We are investigating elevated error rates and increased response times on the Management API across multiple regions. Some operations that depend on it, such as creating new projects, may fail or be slow. This is also causing logins to supabase.com to timeout.
-
We are investigating elevated error rates and increased response times on the Management API across multiple regions. Some operations that depend on it, such as creating new projects, may fail or be slow.
Fixed Project lifecycle operation errors in the EU region
-
Error rates have remained at normal levels following the mitigation. This incident is now resolved.
-
Error rates remain at normal levels. We’re continuing to monitor to confirm sustained stability before resolving this incident.
-
We identified increased error rates in project lifecycle operations (create, restore, pauses, etc.) in the EU region since 21 Oct 23:00 UTC. A mitigation has been put in place and error rates have reduced to normal levels. We are monitoring the situation and are working on fixing affected projects.
Fixed Intermittent connection errors via the connection pooler in us-east-1
-
Between 22:10 and 22:51 UTC on October 9, 2026, about 1% of new database connections made through the Shared Pooler (Supavisor) in us-east-1 failed with "Failed to connect to database" timeout errors. The cause of the failures was an incident at our cloud provider which affected network traffic between availability zones. Supabase Project databases were not affected, and connections that had already been open prior to the incident remained open. The issue was resolved at 22:51 UTC. Clients that retried on connection errors would have reconnected successfully.
Fixed Project lifecycle operations such as project creation, pausing, and restoration, in all regions
-
The issue affecting project lifecycle operations, including project creation, pausing, and restoration, has been resolved. We have observed a reduction in project lifecycle job failures following the fix and confirmed that operations have returned to normal.
-
A fix has been applied, and we have observed a reduction in project lifecycle job failures. We are continuing to monitor the recovery to ensure normal operations remain stable.
-
We are investigating an issue affecting project lifecycle operations such as project creation, pausing, and restoration, in all regions. We’ll provide further updates as more information becomes available.
Fixed Projects stuck in restarting state
-
All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.
-
The fix has fully rolled out. Projects are no longer stuck in a restarting state. We will continue to monitor the situation.
-
We continue with rolling out the fix to affected projects. No new projects are affected and we will provide further updates as the rollout progresses. Our next update will be in 2 hours.
-
We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.
-
We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.
-
We are rolling out a fix to affected projects. We will provide further updates as the rollout progresses.
-
We've identified the root cause of this issue and are working on a fix. We will continue to provide updates as things progress.
-
Some projects in us-east-2 are stuck in restarting state. We are actively investigating this and will provide more updates as information becomes available.
Frequently asked questions
Is Supabase down right now?
No. As of 20:00 UTC on 19 November 2026, Supabase is working normally. If it is not working for you, try the checklist on this page.
When was the last Supabase outage?
The last incident was "Edge Function Issues in ap-northeast-1" on 17 November 2026, fixed after 3 hours 7 minutes.
Why is Supabase not working for me?
If this page shows no problem and few readers report one, the cause is usually local: your connection, a VPN or firewall, an outdated app or a sign-in problem. Work through the checklist above, then report it here so other readers can see it.
Unofficial status page. Teczpert is not affiliated with Supabase. Status data comes from the official status page and is checked every 15 minutes; reports come from readers. Official source: status.supabase.com.