Supabase Outage History

Supabase experienced a 13-hour networking incident caused by their upstream provider that affected users primarily in North and South America, with symptoms including DNS lookup failures and HTTP 530/5XX errors when accessing Supabase projects. The issue impacted multiple components including Auth, Database, Edge Functions, Realtime, Storage, and API Gateway, preventing users from connecting to their projects and experiencing login issues. The incident was resolved after the upstream networking provider identified and implemented fixes across all affected regions, with service gradually improving as mitigations were rolled out region by region.

Supabase experienced delays in transactional email delivery for 22 hours, affecting welcome emails, OAuth approvals, project shutdown notifications, and payment failure alerts. Customers received notifications after their issues were already resolved, such as payment failure alerts arriving after payments were successfully processed. The email queues returned to normal after the team cleared the backlog and addressed the underlying causes of the email spike.

Supabase experienced a major incident where project creation failed in some APAC regions for 1.3 hours, while existing projects remained unaffected. The issue was caused by capacity problems in the impacted regions. The service was fully restored after the team recovered capacity and confirmed project creation was operating normally.

Supabase experienced a major incident where users encountered errors when accessing logs through the dashboard and log drains stopped receiving new logs, affecting the Analytics component for 55 minutes. The underlying logging platform became unstable, preventing proper log retrieval and ingestion while core project functionality remained unaffected. The team restored log sources progressively, with all logging services fully operational after monitoring for stability.

Supabase experienced increased error rates affecting plan upgrades through their dashboard for approximately 1 hour. The issue prevented users from successfully upgrading their service plans. The root cause was identified and a fix was applied, with the service returning to normal operation after monitoring confirmed stability.

Supabase experienced degraded log ingestion that affected their Analytics component for 1 hour. The issue caused some log data to be permanently lost between 11:00 PM and 11:45 PM ETC on March 31. The service was restored after identifying and implementing a fix, with log ingestion returning to normal operation.

Supabase experienced a 48-minute degradation in project creation functionality. The issue prevented users from creating new projects on the platform. The problem was identified and resolved through mitigation steps, with project creation returning to normal operations.

Supabase experienced degraded log ingestion for 1.9 hours, causing delays in current log data and complete log loss for some services including realtime, storage, and api-gateway. The issue was resolved by increasing capacity in targeted areas, though it took additional time to clear the ingestion backlog that had accumulated during the incident.

Supabase experienced network connectivity issues that made Realtime services unavailable for 6 minutes on March 26, 2026. The incident was classified as major and affected the Realtime component. The service was investigating the connectivity problems at the time of the last update.

A permission error in Supabase's branching workflow prevented all users from creating or updating branches for 47 minutes. The issue caused complete failures across the branching functionality. The root cause was identified and a fix was deployed, restoring normal branching access.