Supabase Outage History

Supabase experienced a major incident affecting pause, restore, and backup operations for projects in the us-east-2 (Ohio) region, impacting the Management API. The issue was caused by a problematic deployment and was resolved by redeploying the affected components. The incident lasted 1.2 hours before all operations returned to normal.

Supabase experienced degraded branch creation functionality for 2.7 hours due to database migration locks. The issue was caused by a combination of cluster load, lock contention, and service start-up sequencing problems. Branch creation returned to normal operation and remained stable after resolution.

Supabase experienced login issues for SSO and email accounts on their Dashboard for 2.4 hours, caused by a recent key rotation that triggered "captcha protection: request disallowed (sitekey-secret-mismatch)" errors for users attempting to authenticate. Users already logged in were not affected, and GitHub authentication continued to work normally throughout the incident. The issue was resolved after implementing a fix and monitoring authentication success rates.

Network restrictions prevented read replicas from communicating with their primary databases for a limited number of Supabase customer projects, affecting database functionality for 7.7 hours. The engineering team identified the root cause and developed a fix, which was successfully deployed and monitored for stability. Communication between read replicas and their primaries was fully restored for all impacted projects.

Supabase experienced a UI display issue in the dashboard where paused projects showed incorrect resume deadlines, displaying the current date as the expiry date instead of the actual 90-day deadline. The issue was purely cosmetic and did not affect the ability to resume projects or access project data. The problem was resolved by reverting a recent change that caused the incorrect display.

Supabase experienced a 47-minute log ingestion issue affecting their Analytics component, where customers encountered delayed or unavailable logs. The logging systems returned to normal operation, though some logs from the affected period may not be recoverable despite automatic retry attempts from certain upstream sources. The incident was fully resolved with log delivery returning to normal.

Supabase implemented a time-sensitive update to their Auth service that required users to avoid making any changes to their Auth configurations during the maintenance window. The update was successfully applied after 1.2 hours, with the service monitored for an additional 30 minutes to ensure stability before being fully resolved.

Supabase experienced connectivity issues with project API endpoints that affected the API Gateway component. The incident lasted 38 minutes while the team investigated reports of users being unable to connect to the API endpoints. The issue was resolved after investigation and monitoring.

Supabase experienced connectivity issues affecting Edge Functions for 4.3 hours, where users accessing the service through Mullvad VPN and potentially other VPN providers could not reach Supabase servers due to network disruptions involving a specific colocation/transit provider. The root cause was identified as external network path issues in Western Europe rather than problems with Supabase infrastructure, and the incident was resolved once the external network connectivity was restored.

Supabase experienced issues with customer projects getting stuck during PostgreSQL version upgrades, requiring customers to avoid upgrade attempts during the incident. The engineering team identified the root cause and applied a fix, with most affected projects automatically recovering to their previous healthy state. The incident was resolved after 2.9 hours with upgrade operations returning to normal functionality.