Skip to main content
Menu
Supabase

Incident

Project Lifecycle Issues in ap-northeast-1

Degraded Lasted 4h 48m · started · Supabase's page

DWN-a87efdf88d

Level
confirmed
Worst impact
Degraded
Regions
ap-northeast-1

What to do

  • Check whether you use Supabase in ap-northeast-1. Check your stack

    Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 4h 48m it lasted.

    Anything that failed between 2026-11-11 16:44 UTC and 2026-11-11 21:32 UTC may need a replay.
  • Subscribe to Supabase's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=supabase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Supabase 5

  1. investigating

    Project lifecycle operations have been impacted by an issue in ap-northeast-1. We are investigating along with our upstream provider.

    provider

  2. identified

    The issue has been identified by our upstream provider and is being addressed.

    provider

  3. identified

    Our upstream provider is reporting improvements to project lifecycle actions. We are internally validating the recovery of our systems. We will re-enable functionality after we have confirmed recovery.

    provider

  4. monitoring

    We are seeing recovery of project operations. We will continue to monitor to ensure all project lifecycle functions stabilize.

    provider

  5. resolved

    All operations have returned to normal and have remained stable.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-a87efdf88d

Is Supabase still down?

No, this incident was resolved 2026-11-11 21:32 UTC. For Supabase's live state, see https://down.guide/providers/supabase.

How long did it last?

4h 48m, from 2026-11-11 16:44 UTC to 2026-11-11 21:32 UTC, by the times Supabase posted.

What was affected?

Supabase named in ap-northeast-1.

What caused it?

Supabase hasn't published a root cause. If it does, it shows here.

Where does this come from?

Supabase's official status page, https://status.supabase.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.