Downrightnow
// Incident Post-MortemDRN-D086A04D

Supabase outage on June 24, 2026

Minor severityResolved2h 58mCloud
Started · UTC
Jun 24, 03:59 PM
16h ago
Resolved · UTC
Jun 24, 06:57 PM
13h ago
Duration
2h 58m
End-to-end
Peak confidence
45.00
74 snapshots
// User impact

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

// What happened

Jun 24, 15:59 UTC Investigating - We are aware of a period of degraded performance of the Shared Pooler cluster in ap-southeast-1. Affected projects experienced increased ECHECKOUTTIMEOUT errors when running queries.The window of the incident was between 14:48 to 15:25 UTC. The issue appears to be resolved. We are investigating the cause of this incident and will continue monitoring the cluster.

Deterministic readout · awaiting AI summary pass

// Timeline

  1. Incident detected

    Minor confidence crossed the incident threshold for Supabase: degraded performance of the Shared Pooler cluster in ap-southeast-1.

  2. Marked resolved

    The incident was closed after 2h 58m of observed impact.

  3. Peak confidence reached

    Confidence peaked at 75.00 while the service was marked Operational.

// Signals by source0 sources

No per-source signal payloads were preserved in this incident's snapshot window.

// Aggregate evidence

Confidence scoring

45.00

The incident reached 45.00 peak confidence across 74 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 Wed, Jun 24, 2026, 06:57 PM UTC.