Minor impactResolvedDatabases

Supabase incident: Project creations are degraded in multiple regions

Supabase reported this minor-impact incident on its official status page on Sep 22, 2026, 08:33 UTC. It was resolved after 31 min.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Sep 22, 2026, 08:33 UTC
started
Sep 22, 2026, 09:05 UTC
resolved
31 min
duration
Minor
impact

Timeline

updates from Supabase's status page ↗
  1. resolvedSep 22, 2026, 09:05 UTC

    The latency has recovered and the incident is now resolved.

  2. monitoringSep 22, 2026, 08:33 UTC

    We have identified increased latency in Project creations in these regions from 0730 UTC to 0805 UTC: ap-northeast-1 ap-northeast-2 eu-central-1 eu-central-2 eu-north-1 eu-west-1 eu-west-3 us-west-1 The latency has since recovered and our teams are monitoring for full recovery. Existing project availability has not been impacted.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Supabase have incidents?

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

← Previous: Project Lifecycle Activity Degradation (Sep 19, 2026)Next: Supavisor connection disruptions in EU West 1 (Ireland) (Sep 22, 2026) →
Supabase incident on Sep 22, 2026: Project creations are degraded in multiple regions · APIStatus.watch