Isitreallydown?
// Incident Post-MortemDRN-65634D0F

Supabase outage on May 8, 2026

Minor severityResolved45 minCloud
Started · UTC
May 08, 01:26 PM
4d ago
Resolved · UTC
May 08, 02:11 PM
4d ago
Duration
45 min
End-to-end
Peak confidence
45.00
18 snapshots
// What happened

Supabase’s official status page is reporting a major problem affecting Network connectivity in us-east-1-az4 (US East, Northern Virginia). Isitreallydown? hasn’t been able to run recent connection tests yet; DNS is resolving normally and other signals are quiet, so this currently looks like localized regional degradation rather than a broad Supabase-wide outage (Telemetry confidence: low). Supabase also has scheduled maintenance posted for “Shared Pooler scheduled maintenance in ap-southeast-1” (Singapore) on 2026-05-13 and “Shared Pooler scheduled maintenance in sa-east-1” (São Paulo, Brazil) on 2026-05-14.

Cached · Sat, May 09, 2026, 06:33 PM UTC · scope: service signals

// Timeline

  1. Status changed to Operational

    The stored readout moved to Operational with confidence 55.00.

  2. Incident detected

    Minor confidence crossed the incident threshold for Customer Projects Experiencing Upgrade Issues.

  3. Marked resolved

    The incident was closed after 45 min of observed impact.

  4. Peak confidence reached

    Confidence peaked at 60.00 while the service was marked Operational.

// Signals by source1 sources
  • Official status

    Status.Supabase.Com reported an open incident — Customer Projects Experiencing Upgrade Issues · impact: minor

    01:33 PM UTC
// Aggregate evidence

Confidence scoring

45.00

The incident reached 45.00 peak confidence across 18 stored status snapshots.

User reports

0 / 15m

No elevated user-report volume was preserved in the incident window snapshots.

Status samples

0 affected

The incident row exists, but the bounded snapshot window does not include affected status samples.

Recovery signal

Resolved

Recovery was recorded at Fri, May 08, 2026, 02:11 PM UTC.

// User impact

Supabase users likely saw failed connections, degraded availability, or session instability for this Cloud service. The incident reached Minor severity and lasted 45 min. The stored report window does not show a preserved user-report spike.