Supabase outage on April 18, 2026
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
Incident detected
Minor confidence crossed the incident threshold for Increased Errors on HTTP Endpoints.
Marked resolved
The incident was closed after 45 min of observed impact.
No per-source signal payloads were preserved in this incident's snapshot window.
Confidence scoring
25.00The incident reached 25.00 peak confidence across available 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 Sat, Apr 18, 2026, 02:46 AM UTC.
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.