Minor impactResolvedDatabases

Supabase incident: Degraded project creation success rates in the ca-central-1 region

Supabase reported this minor-impact incident on its official status page on Jul 2, 2026, 22:59 UTC. It was resolved after 5h 52m.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Jul 2, 2026, 22:59 UTC
started
Jul 3, 2026, 04:51 UTC
resolved
5h 52m
duration
Minor
impact

Timeline

updates from Supabase's status page ↗
  1. resolvedJul 3, 2026, 04:51 UTC

    The project creation in ca-central-1 has been restored.

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 47 incidents in the last 90 days, 17 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history

← Previous: Errors when attempting to view advisor results in the Supabase dashboard (Jul 2, 2026)Next: Endpoints in Americas regions returning 500 Internal server error (Jul 6, 2026) →
Supabase incident on Jul 2, 2026: Degraded project creation success rates in the ca-central-1 region · APIStatus.watch