Minor impactResolvedDatabases

Supabase incident: Supabase CLI CI workflow failures

Supabase reported this minor-impact incident on its official status page on Sep 23, 2026, 21:58 UTC. It was resolved after 1h 42m.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Sep 23, 2026, 21:58 UTC
started
Sep 23, 2026, 23:41 UTC
resolved
1h 42m
duration
Minor
impact

Timeline

updates from Supabase's status page ↗
  1. resolvedSep 23, 2026, 23:41 UTC

    This incident has been resolved.

  2. monitoringSep 23, 2026, 22:56 UTC

    We are no longer seeing rate limiting issues affecting Supabase CLI CI workflows. We're continuing to monitor the service for stability while we roll out a fallback patch to improve resilience and help prevent the issue from recurring.

  3. identifiedSep 23, 2026, 22:36 UTC

    We've identified the cause and are working on a fix.

  4. investigatingSep 23, 2026, 21:58 UTC

    We're seeing rate limiting issues causing Supabase CLI CI workflow failures

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: Storage search failing for restored projects (Sep 23, 2026)Next: Permission errors in the Supabase Dashboard (Sep 24, 2026) →
Supabase incident on Sep 23, 2026: Supabase CLI CI workflow failures · APIStatus.watch