Supabase Outage History

Supabase experienced degraded logging ingestion across all regions for 2.5 hours, causing delays, errors, and partial or missing log data in the Analytics component. Users encountered issues accessing logs while core project functionality remained unaffected. The engineering team identified the root cause, implemented a fix, and restored normal logging ingestion across all regions.

Supabase experienced elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region for 1.5 hours. The issue was resolved through a controlled redeployment of the affected services. Error rates returned to normal and the system resumed stable operation.

Supabase experienced project creation failures across multiple regions due to issues with their Management API. Users were unable to create new projects in any region for approximately 1.2 hours. The issue was identified and resolved with a fix that restored successful project creation functionality across all regions.

Supabase experienced elevated error rates in their storage services within the ap-northeast-1 (Tokyo) region for 2 hours, primarily affecting newly created projects' ability to connect to storage while existing projects remained unaffected. The engineering team identified the root cause as issues with task instances and batch sending events, and successfully implemented a fix to restore normal connectivity for all projects in the region.

Supabase experienced issues where custom Postgres configurations applied through the CLI were not taking effect for projects running Postgres version 17.6.1.084. Only projects using CLI-managed configurations on this specific Postgres version were affected, while projects on earlier versions or not using CLI configuration management remained unaffected. The incident was resolved after 2.9 hours with a fix implemented and monitored.

Supabase experienced increased error rates with their Connection Pooler service in the ap-northeast-2 (South Korea) region for 1.5 hours. The issue affected database connectivity for users in that region. The team implemented a fix that reduced error rates, and connectivity was fully stabilized after monitoring confirmed the resolution.

Supabase experienced a major incident where users were unable to create new projects due to issues with the Management API. The incident lasted 1.1 hours, during which project creation operations consistently failed across all regions. The root cause was identified and fixed, with project creation functionality fully restored and error rates returning to normal levels.

Supabase experienced degraded storage operations in the EU-Central-2 region, affecting file uploads and downloads for 1.8 hours. The issue was caused by an upstream provider problem, which was identified and resolved. All storage operations returned to normal functionality after the upstream incident was fixed.

Supabase experienced elevated error rates in their Management API across all regions for 2 hours, preventing users from creating new projects, accessing dashboard functions, and making configuration changes. Existing projects and their data connections remained fully operational throughout the incident. The team identified the root cause, deployed mitigations, and restored all services to normal operation.

Supabase experienced issues with their billing system that prevented users from changing subscription plans or creating paid organizations for 1.9 hours. The problem was caused by their upstream billing provider, requiring Supabase to temporarily disable these features while working with the provider on a resolution. The issue was resolved after the upstream provider applied a fix, restoring full functionality to subscription management.