Live  /  Supabase  /  Incident

Supabase: Project Lifecycle Issues in ap-northeast-1

Supabase · supabase.comMinor incidentResolved2026-11-11 21:32 UTC
Public — what happened

Summary

Supabase said that starting at 16:44 UTC on 2026-11-11, operations for managing projects, such as lifecycle actions, were affected in its ap-northeast-1 region, and it began looking into the problem together with its upstream provider. By 17:05 UTC it said that provider had identified the issue and was working on it. Supabase reported later that the provider was seeing improvements, and that it was checking its own systems before turning functionality back on. At 18:39 UTC it said project operations were recovering and that it was monitoring to make sure everything stays stable, so the incident was not yet marked resolved.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 47, 2026, our weekly internet health report.

The full archive is on the Supabase status & history page.

Related: Supabase status & history. SquidGrid is not affiliated with Supabase.