Critical impactResolvedDatabases

Supabase outage: Project access, updating and creation impacted in us-east-2

Supabase reported this critical-impact incident on its official status page on Aug 14, 2026, 09:31 UTC. It was resolved after 1h 14m.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Aug 14, 2026, 09:31 UTC
started
Aug 14, 2026, 10:44 UTC
resolved
1h 14m
duration
Critical
impact

Affected components

  • us-east-2
  1. resolvedAug 14, 2026, 10:44 UTC

    This incident has been resolved.

  2. monitoringAug 14, 2026, 09:59 UTC

    A fix has been applied to all impacted projects in us-east-2. We are monitoring for full resolution.

  3. identifiedAug 14, 2026, 09:49 UTC

    A fix is being rolled out and we are seeing improved performance across impacted projects. We are continuing to roll out the full fix and will be confirming recovery asap.

  4. identifiedAug 14, 2026, 09:31 UTC

    We are investigating an issue of project creation and updating in us-east-2. A fix is under review and prepared for being rolled out.

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

Supabase outage on Aug 14, 2026: Project access, updating and creation impacted in us-east-2 · APIStatus.watch