Live / Supabase / Incident
Supabase: Project creation errors ap-ne1
Supabase · supabase.comMinor incidentResolved2026-10-17 07:49 UTC
Public — what happened
Summary
Supabase reported a minor incident beginning at 06:27 UTC on 2026-10-17 in which customers could get errors when creating or unpausing a project in its ap-northeast-1 region. The company said it linked the problem to an outage at an upstream provider and was redirecting traffic to other regions while waiting for that provider to update. At 07:16 UTC Supabase said the provider had confirmed its issue was fixed, and the company began moving project creation traffic back and watching for full recovery. The incident was marked resolved at 07:49.
Timeline
- Started — 2026-10-17 06:27 UTC
- Identified — 2026-10-17 06:27 UTC
- Monitoring — 2026-10-17 07:16 UTC
- Resolved — 2026-10-17 07:49 UTC · 1h 22m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Supabase against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Supabase: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Supabase report →
More from Supabase
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.