Supabase Outage History

Supabase Edge Functions experienced high response times in the ap-northeast-1 (Tokyo) and ap-northeast-2 (Seoul) regions for 5.2 hours. The incident affected Edge Functions performance in these Asia Pacific regions, causing service disruption for users. The issue was resolved through mitigation efforts that were first applied to Tokyo, then rolled out to Seoul, with both regions returning to normal operation.

Supabase's Dashboard and Management API became inaccessible for 2.8 hours due to a problematic change that was later identified and reverted. Existing user projects remained unaffected and continued to function normally throughout the incident. The service was fully recovered and monitored before being marked as resolved.

Supabase experienced increased database operation errors in the us-east-2 region affecting a subset of projects for 4.4 hours. The incident impacted database functionality, with users able to manually resolve issues by restarting their projects through the dashboard. The root cause was addressed with most projects automatically fixed, though a handful required manual intervention from Supabase staff.

Supabase Edge Functions experienced widespread 504 errors across multiple regions for 1.5 hours due to a denial-of-service event. The incident was classified as major and affected Edge Functions' ability to process requests normally. The team identified the root cause, implemented corrective measures and mitigations to restore stability, with users confirming Edge Functions returned to normal operation.

Supabase experienced connectivity issues with their Supavisor connection pooler in the EU-Central-1 region, while Data API, direct connections, and dedicated pooler connections remained unaffected. The incident lasted 1.1 hours, with connection and query times returning to normal levels before the team confirmed full resolution after monitoring for stability.

Supabase experienced delays in project pausing and read replica configuration changes in the EU-West-1 region due to a spike in queued jobs that caused processing backlogs. All existing projects remained operational and accessible throughout the incident. The issue was resolved after 2.5 hours once the job queue was processed and optimizations were implemented to improve processing speed.

Users in India experienced network connectivity problems accessing Supabase services, including Auth and Edge Functions, due to ISP-level DNS resolution issues and access restrictions by local authorities. The incident lasted over 8 days and prevented users from connecting to their Supabase projects, though the infrastructure remained fully operational and projects were accessible from outside India. The issue was resolved through engagement with the Ministry of Electronics and Information Technology (MeitY), with full access restored and users advised to clear DNS cache or use workarounds like alternative DNS providers or VPNs during the incident.

Supabase experienced a 6.6-hour metrics collection issue in the US-West-2 region that prevented users from viewing project metrics in the dashboard and delayed automatic functions like disk resizes. The team deployed additional capacity to restore metrics collection operations and continued monitoring until full stability was confirmed. Project availability and core functionality remained unaffected throughout the incident.