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
Maintenance: Scheduled maintenance: Shared Pooler (Supavisor), eu-central-2
Status: Scheduled (Mon, 30 Nov 2026 13:00:00 GMT - Mon, 30 Nov 2026 15:00:00 GMT) We will perform scheduled maintenance on the Shared Pooler (Supavisor) in the eu-central-2 region on Monday, November 30, from 13:00 to 15:00 UTC. During the window, existing client connections may be dropped, and you may briefly see connection errors while traffic switches to the new version. Applications that reconnect and retry automatically will recover without action. Direct database connections and the Dedicated Pooler are not affected. Affected components eu-central-2 (Under maintenance)
Elevated Error rates for All Supabase project APIs
Status: Resolved This issue has been resolved. All API routes are operating normally, and we are no longer observing elevated error rates. Affected components Auth (Operational) eu-west-2 (Operational) ap-east-1 (Operational) eu-central-1 (Operational) eu-central-2 (Operational) us-west-1 (Operational) eu-west-1 (Operational) ap-east-1 (Operational) us-east-2 (Operational) eu-north-1 (Operational) ap-southeast-2 (Operational) ca-central-1 (Operational) ap-northeast-1 (Operational) ap-south-1 (Operational) ap-northeast-2 (Operational) ap-east-1 (Operational) ap-northeast-2 (Operational) eu-west-3 (Operational) ap-northeast-1 (Operational) ap-southeast-1 (Operational) us-west-2 (Operational) sa-east-1 (Operational) us-east-1 (Operational) ap-southeast-2 (Operational) ca-central-1 (Operational) us-west-2 (Operational) eu-north-1 (Operational) ap-southeast-1 (Operational) eu-west-3 (Operational) sa-east-1 (Operational) eu-central-1 (Operational) eu-central-1 (Operational) eu-west-2 (Operational) ap-northeast-2 (Operational) ap-southeast-2 (Operational) eu-west-1 (Operational) us-east-2 (Operational) ca-central-1 (Operational) eu-west-1 (Operational) sa-east-1 (Operational) eu-central-2 (Operational) us-east-1 (Operational) eu-west-2 (Operational) ap-northeast-1 (Operational) us-east-2 (Operational) ap-south-1 (Operational) ap-southeast-1 (Operational) us-west-1 (Operational) eu-north-1 (Operational) us-east-1 (Operational) us-west-2 (Operational) eu-central-2 (Operational) us-west-1 (Operational) eu-west-3 (Operational) ap-south-1 (Operational)
Database Connection Errors
Status: Resolved 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. Affected components ap-southeast-1 (Operational) ap-south-1 (Operational) us-west-1 (Operational) ap-northeast-2 (Operational) eu-north-1 (Operational) ca-central-1 (Operational) us-west-2 (Operational) eu-central-1 (Operational) ap-southeast-2 (Operational) eu-west-1 (Operational) us-east-2 (Operational) eu-west-2 (Operational) sa-east-1 (Operational) eu-central-2 (Operational) ap-northeast-1 (Operational) eu-west-3 (Operational) ap-east-1 (Operational) us-east-1 (Operational)
Storage request degradation in eu-west-1
Status: Resolved 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. Affected components eu-west-1 (Operational)
Project Lifecycle Issues in ap-northeast-1
Status: Resolved All operations have returned to normal and have remained stable. Affected components ap-northeast-1 (Operational) ap-northeast-1 (Operational) ap-northeast-1 (Operational) ap-northeast-1 (Operational)
Interruption in connections to Supavisor in eu-west-2
Status: Resolved The interruption to Supavisor connections in eu-west-2 has been resolved. Monitoring has confirmed that systems have recovered and connections are operating normally.
Increased Errors with Project Lifecycle Operations in US-West-2
Status: Resolved 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. Affected components us-west-2 (Operational) us-west-2 (Operational) us-west-2 (Operational) us-west-2 (Operational)
Intermittent 502/503 errors for pg_net calls to Edge Functions
Status: Resolved The issue has been resolved, and pg_net calls to Edge Functions in ap-southeast-1 are now operating normally. Affected components ap-southeast-1 (Operational)
Storage issues in us-east-1 and eu-central-1
Status: Resolved The incident has been resolved. Affected components eu-central-1 (Operational) us-east-1 (Operational)
Intermittent errors on Supavisor Shared Pooler in us-east-2
Status: Resolved Errors have subsided and connections are back to normal. Affected components us-east-2 (Operational)
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.