Supabase outage on May 20, 2026
Supabase users likely saw failed connections, degraded availability, or session instability for this Cloud service. The incident reached Minor severity and lasted 6h 1m. The stored report window does not show a preserved user-report spike.
Supabase's official status page is reporting a minor disruption and partially degraded service, with identified issues regarding network restrictions for read replica communication and access problems from some providers in Brazil. Outside of these specific database and regional connectivity issues, Downrightnow’s checks show DNS is resolving normally and user reports remain quiet. Several scheduled maintenances are also planned for Connection Pooler upgrades across multiple regions including us-east-1, us-west-1, and Europe starting in late May.
Cached · Thu, May 21, 2026, 03:06 AM UTC · scope: this incident
Status changed to Operational
The stored readout moved to Operational with confidence 75.00.
Peak confidence reached
Confidence peaked at 75.00 while the service was marked Operational.
Incident detected
Minor confidence crossed the incident threshold for Supabase: network restrictions preventing read replica communication.
Status changed to Degraded Performance
The stored readout moved to Degraded Performance with confidence 34.00.
Marked resolved
The incident was closed after 6h 1m of observed impact.
No per-source signal payloads were preserved in this incident's snapshot window.
Confidence scoring
45.00The incident reached 45.00 peak confidence across 68 stored status snapshots.
User reports
0 / 15mNo elevated user-report volume was preserved in the incident window snapshots.
Status samples
0 affectedThe incident row exists, but the bounded snapshot window does not include affected status samples.
Recovery signal
ResolvedRecovery was recorded at Thu, May 21, 2026, 03:05 AM UTC.