Minor impactResolvedDatabases

Supabase incident: Project creation errors ap-ne1

Supabase reported this minor-impact incident on its official status page on Oct 17, 2026, 06:27 UTC. It was resolved after 1h 22m.

Right now Supabase is operational. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Oct 17, 2026, 06:27 UTC
started
Oct 17, 2026, 07:49 UTC
resolved
1h 22m
duration
Minor
impact
  1. resolvedOct 17, 2026, 07:49 UTC

    Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.

  2. monitoringOct 17, 2026, 07:16 UTC

    Our upstream partner has confirmed the issue is resolved. We are working to restore project creation traffic back to the region and monitor for full recovery in ap-northeast-1.

  3. identifiedOct 17, 2026, 06:27 UTC

    Due to an ongoing upstream provider outage, we are remediating project creation errors in apne-1. Customers may see errors in creating or unpausing a project from this region. We are working to re-direct traffic to non-impacted regions and awaiting updates from our dependant provider.

What APIStatus.watch saw

  • Oct 17, 2026, 06:30 UTCoperational → degraded
  • Oct 17, 2026, 07:20 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Supabase have incidents?

Supabase reported 65 incidents in the last 90 days, 24 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history