Is Supabase Down?
Real-time status check for supabase.com
Checking status...
About Supabase Status
BlueMonitor checks Supabase (supabase.com) by sending automated requests to its servers. If the service responds within a normal timeframe and returns a successful status code, it's marked as operational. Response times over 3 seconds indicate the service is slow, and connection failures or server errors indicate the service may be down.
Recent Incidents
Storage users in US-West-2 experiencing increased latency on storage requests
Jun 13 , 00:40 UTC Resolved - All residual jobs have drained. Storage performance and job activity is normal. Jun 12 , 23:57 UTC Update - Job queues continue to drain. We will actively monitor until they are complete. Jun 12 , 20:26 UTC Monitoring - Backlog is being effectively processed and operations have returned to normal. We continue to monitor the performance in us-west-2. Jun 12 , 19:30 UTC Update - We are seeing improvement in the performance of us-west-2 after implementation of our mitigation strategies. Storage operation is returning to normal. We will continue to monitor performance in this region. Jun 12 , 18:28 UTC Update - We have implemented further mitigations and are tracking their progress. We continue to actively work this issue. Jun 12 , 17:29 UTC Update - The team is still working on a solution, and mitigation work is underway. Jun 12 , 16:30 UTC Update - We are implementing load mitigation strategies to improve the performance of storage requests in US-West-2. Jun 12 , 16:00 UTC Identified - Users in US-West-2 are seeing increased latency on storage requests. The team has identified the issue and is working on a solution.
Higher connection failure rate for ap-northeast-1 and ap-northeast-2
Jun 10 , 00:00 UTC Resolved - From 00:52 to 01:02 UTC on 10th June an internal deployment in one of the ap-northeast-1 and ap-northeast-2 clusters caused a higher connection failure rate. Users would have experienced failing connections, increased query latency and would not have been able to retrieve pooler metrics. The deployment has now been reverted and full service availability restored.
Upgrade Shared Pooler V1 to V2 for eu-west-2 region
Jun 9 , 15:00 UTC Completed - The scheduled maintenance has been completed. Jun 9 , 13:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun 2 , 00:56 UTC Scheduled - There will be a scheduled maintenance on 2026-06-09 from 13:00-15:00 UTC on the Shared Pooler(V1) for the eu-west-2 region. This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime. The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected: Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format: aws-0-eu-west-2-pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-1-eu-west-2.pooler.supabase.com are not affected by this maintenance. Please follow the status page for updates.
DNS Resolution Failures for TLD .co users
Jun 12 , 11:09 UTC Update - Our upstream TLD provider is continuing to make changes to its network routing policies to address this issue. These changes are intended to improve regional traffic routing and reduce DNS resolution failures. We have already begun to see improvements as these changes take effect, but the issue has not yet been fully resolved. We are continuing to monitor the situation closely and work with the provider toward a complete resolution. We will provide another update as soon as more information becomes available. Jun 10 , 23:24 UTC Update - Our upstream TLD provider believes they have identified the underlying issue, and we are continuing to coordinate with them to review their findings and potential remediation options. In parallel, we are investigating other factors that may be contributing to the ongoing resolution problems affecting a subset of customers. VPNs continue to provide a workaround for impacted end users while our investigation remains ongoing. Jun 8 , 17:32 UTC Update - We have opened a follow-up issue with our provider to address the continued problems a subset of our customers in the Americas are experiencing with top-level ".co" domain resolution. We will continue to pursue this issue until it is resolved and customers who have reported the issue are able to correctly resolve the domain name. Jun 8 , 12:38 UTC Update - Our testing has observed that the issue is related to selected ISP resolvers to .co domains. The clients impacted are mainly located in us-east-1, us-east-2 region. We continue to review this issue for resolution with our third party network partner. Jun 8 , 06:37 UTC Monitoring - The third-party has confirmed a fix has been implemented and we are validating the results with our impacted users. Jun 8 , 03:39 UTC Identified - We are investigating reports of DNS resolution failures affecting a subset of customers connecting to Supabase project endpoints. This appears to be related to a third-party issue with .c
Errors impacting pause, restore, and backup operations in us-east-2 (Ohio)
Jun 2 , 14:41 UTC Resolved - All operations have continued as normal since moving this incident to Monitoring. We are resolving this incident. Jun 2 , 14:12 UTC Monitoring - The redeployment has returned pause, restore and backup operations in the affected region to normal. We will continue to monitor for any residual impact. Jun 2 , 14:05 UTC Identified - We have identified the cause is related to a recent deployment. We have initiated a redeploy to address the issue. Jun 2 , 13:36 UTC Investigating - We are currently investigating an issue affecting pause, restore, and backup operations for projects in us-east-2 (Ohio) We will provide further updates as more information becomes available.
Upgrade Shared Pooler V1 to V2 for us-east-1 region
Jun 3 , 15:00 UTC Completed - The scheduled maintenance has been completed. Jun 3 , 13:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 28 , 19:24 UTC Update - We will be undergoing scheduled maintenance during this time. May 18 , 02:57 UTC Scheduled - There will be scheduled maintenance on 2026-06-03 from 13:00-15:00 UTC (09:00-11:00 EDT) on the Shared Pooler(V1) for the us-east-1 region. This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime. The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected: Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format: aws-0-us-east-1-pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-1-us-east-1.pooler.supabase.comare not affected by this maintenance. Please follow the status page for updates.
Upgrade Shared Pooler V1 to V2 for us-west-1 region
Jun 2 , 18:00 UTC Completed - The scheduled maintenance has been completed. Jun 2 , 15:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 28 , 19:25 UTC Update - We will be undergoing scheduled maintenance during this time. May 27 , 16:56 UTC Update - We will be undergoing scheduled maintenance during this time. May 22 , 15:54 UTC Update - We will be undergoing scheduled maintenance during this time. May 18 , 02:55 UTC Scheduled - There will be scheduled maintenance on 2026-06-02 from 15:00-18:00 UTC (08:00-11:00 PDT) on the Shared Pooler(V1) for the us-west-1 region. This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime. The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected: Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format: aws-0-us-west-1-pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-1-us-west-1.pooler.supabase.comare not affected by this maintenance. Please follow the status page for updates.
Upgrade Shared Pooler V1 to V2 for eu-west-1 region
Jun 1 , 15:00 UTC Completed - The scheduled maintenance has been completed. Jun 1 , 13:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 28 , 19:25 UTC Update - We will be undergoing scheduled maintenance during this time. May 18 , 02:52 UTC Scheduled - There will be a scheduled maintenance on 2026-06-01 from 13:00-15:00 UTC on the Shared Pooler(V1) for the eu-west-1 region. This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime. The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected: Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format: aws-0-eu-west-1-pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-1-eu-west-1.pooler.supabase.com are not affected by this maintenance. Please follow the status page for updates.
Upgrade Shared Pooler V1 to V2 for eu-central-1 region
May 26 , 15:00 UTC Completed - The scheduled maintenance has been completed. May 26 , 13:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 23 , 04:39 UTC Update - We will be undergoing scheduled maintenance during this time. May 18 , 02:49 UTC Scheduled - There will be a scheduled maintenance on 2026-05-26 from 13:00-15:00 UTC on the Shared Pooler(V1) for the eu-central-1 region. This maintenance upgrades the Shared Pooler to a new version (V2) that provides better scalability and uptime. The Shared Pooler will be unavailable during this time period for anyone connecting to their projects using it. Your projects remain available and connections via the Dedicated Pooler and Direct Connections will continue to work. How to determine whether you are affected: Only projects connecting to V1 of the Shared Pooler are affected. If your connection string has the format: aws-0-eu-central-1-pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-eu-central-1.pooler.supabase.com are not affected by this maintenance. Please follow the status page for updates.
Branch creation degradation
May 21 , 19:26 UTC Resolved - Branch creation continues to be stable. May 21 , 18:54 UTC Monitoring - Branch creation has returned to normal. We are investigating a set of factors that likely contributed to the degradation, including cluster load, lock contention, and service start-up sequencing to identify areas for improvement going forward. We will monitor our platform for another 30 minutes to ensure the problem has fully resolved before resolving the incident. May 21 , 17:45 UTC Update - We continue investigating different possible underlying causes and will provide updates as progress is made. May 21 , 16:46 UTC Investigating - We are seeing degradation in branch creation linked to database migration locks. We are investigating and will share further updates as progress is made.
Frequently Asked Questions
Is Supabase down right now?
This page shows the real-time status of Supabase. The status is checked automatically by pinging Supabase's servers. If the status shows "Down", it means Supabase is currently experiencing issues.
Why is Supabase not working?
Supabase may not be working due to server outages, scheduled maintenance, network issues, or high traffic. Check the current status above for real-time information.
How do I check if Supabase is down for everyone?
BlueMonitor checks Supabase's servers from our monitoring infrastructure. If the status shows "Down" here, it's likely down for everyone. If it shows "Up" but you can't access it, the issue may be on your end.
What should I do if Supabase is down?
If Supabase is down, you can: wait a few minutes and try again, check their official social media for updates, clear your browser cache, or try using a different network connection.