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
Auth Service Update
May 15 , 19:18 UTC Resolved - All changes hav been applied. May 15 , 18:47 UTC Monitoring - The update has been implemented. Service changes can be made. We will monitor the effect for the next 30 minutes to ensure stability. May 15 , 18:11 UTC 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.
Shared Pooler scheduled maintenance in sa-east-1
May 14 , 20:00 UTC Completed - The scheduled maintenance has been completed. May 14 , 18:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 7 , 22:16 UTC Scheduled - There will be scheduled maintenance on May 14 from 18:00-20:00 UTC (15:00-17:00 BRT) on the Shared Pooler(V1) for the sa-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-sa-east-1.pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-1-sa-east-1.pooler.supabase.com are not affected by this maintenance. Please follow the status page for updates.
Access Issues From Some Providers in Brazil
May 14 , 22:23 UTC 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. May 14 , 16:37 UTC Update - 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. May 14 , 15:54 UTC Update - 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. May 14 , 15:34 UTC 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
May 14 , 14:56 UTC Investigating - We are investigating reports of connectivity issues to project API endpoints.
Edge Traffic Issues
May 13 , 20:35 UTC Resolved - We've determined that the connectivity issues are isolated to users accessing Supabase through Mullvad VPN and potentially other VPN providers. The root cause appears to be network disruptions involving a specific colocation/transit provider used by Mullvad, rather than an issue with Supabase or Cloudflare infrastructure. We've reached out to Mullvad support, but as this is dependent on external providers, there are no further mitigation steps we can take internally. Users experiencing issues are advised to avoid affected VPN networks or contact their VPN provider directly for support. The incident is now resolved May 13 , 19:50 UTC 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. May 13 , 17:31 UTC Update - 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. May 13 , 16:46 UTC Update - 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. May 13 , 16:15 UTC Investigating - We've observed traffic from upstream providers of
Shared Pooler scheduled maintenance in ap-southeast-1
May 13 , 09:00 UTC Completed - The scheduled maintenance has been completed. May 13 , 07:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 7 , 22:13 UTC Scheduled - There will be scheduled maintenance on May 13 from 7:00-9:00 UTC (15:00-17:00 SGT) on the Shared Pooler(V1) for the ap-southeast-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-ap-southeast-1.pooler.supabase.com, you can expect to see errors during the maintenance. Those using connection strings with the format: aws-1-ap-southeast-1.pooler.supabase.com are not affected by this maintenance. Please follow the status page for updates.
Customer Projects Experiencing Upgrade Issues
May 8 , 16:13 UTC Resolved - Upgrade operations have returned to normal. May 8 , 14:39 UTC 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. May 8 , 13:46 UTC Update - 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 resolved. We will continue to provide updates as information becomes available. May 8 , 13:26 UTC Update - We are continuing to work on a fix for this issue. May 8 , 13:25 UTC 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
May 9 , 04:49 UTC Resolved - Recovery efforts are completed and this incident is now resolved. Thank you for your patience throughout this incident. May 9 , 04:34 UTC 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. May 9 , 04:10 UTC Update - 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 progresses. May 9 , 01:32 UTC Update - 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 updates as more information becomes available. May 8 , 16:34 UTC Update - 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 provid
Edge Functions scheduled maintenance in eu-central-1 and us-east-1
May 4 , 05:00 UTC Completed - The scheduled maintenance has been completed. May 4 , 04:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 1 , 17:18 UTC Scheduled - Upstream provider regular scheduled maintenance on instances in us-east-1 and eu-central-1. We do not expect downtime or impact to Edge Functions invocations or deploys during this window. We will monitor and update its progress.
Supavisor connectivity in eu-central-1
May 3 , 22:30 UTC Resolved - From 15:30 to 7:00 UTC, for projects in eu-central-1, a Supavisor node experienced connectivity issues and was not able to connect to customer databases, causing checkout timeouts and auth query failed errors. This has been resolved and Supavisor is fully available.
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.