Is Supabase down?
UpAll Systems Operational · checked 37m ago
0 Reddit outage posts · last 24h
Reports, last 24 hours
Supabase users may have encountered errors when their apps tried to access Supabase projects. The issue is now resolved, and all affected connections are working normally.
official update →Supabase had a minor issue causing database connection errors for users in affected regions. The issue is now resolved, and services have recovered across all affected regions.
official update →Supabase’s file storage service had minor problems handling requests for users in the eu-west-1 region. The issue has been fixed, and no further problems were seen during monitoring.
official update →All operations have returned to normal and have remained stable.
official update →The interruption to Supavisor connections in eu-west-2 has been resolved. Monitoring has confirmed that systems have recovered and connections are operating normally.
official update →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.
official update →The issue has been resolved, and pg_net calls to Edge Functions in ap-southeast-1 are now operating normally.
official update →The incident has been resolved.
official update →Errors have subsided and connections are back to normal.
official update →Connection Logging feature is working fine for all customers now.
official update →Storage uploads have remained stable, and this issue is now resolved.
official update →This issue is now resolved.
official update →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
official update →This issue has been resolved and log delivery is operational again.
official update →This issue is now resolved.
official update →This issue has been resolved and our response times are back to operational.
official update →Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.
official update →Error rates have remained at normal levels following the mitigation. This incident is now resolved.
official update →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.
official update →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.
official update →All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.
official update →Ticket creation has remained normal. We re resolving this incident.
official update →Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.
official update →