Supabase incident

Some Users Experiencing Connectivity issues via Supavisor in EU-Central-1

Major Resolved View vendor source →

Supabase experienced a major incident on February 26, 2026 affecting Connection Pooler, lasting 1h 1m. The incident has been resolved; the full update timeline is below.

Started
Feb 26, 2026, 12:12 AM UTC
Resolved
Feb 26, 2026, 01:14 AM UTC
Duration
1h 1m
Detected by Pingoru
Feb 26, 2026, 12:12 AM UTC

Affected components

Connection Pooler

Update timeline

  1. investigating Feb 26, 2026, 12:12 AM UTC

    The team is investigating connectivity issues via Supavisor in EU-Central-1. Data API, direct connections, and connections via the dedicated pooler are unaffected. You can read more on the dedicated pooler here: https://supabase.com/docs/guides/database/connecting-to-postgres#dedicated-pooler

  2. monitoring Feb 26, 2026, 12:47 AM UTC

    Connection and query times are back to normal levels. We will continue monitoring to ensure stability.

  3. resolved Feb 26, 2026, 01:14 AM UTC

    Systems have remained stable, and we are confident the issue has been resolved.