Minor impactResolvedDatabases

Supabase incident: DNS creation delays

Supabase reported this minor-impact incident on its official status page on Jul 31, 2026, 12:27 UTC. It was resolved after 58 min.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Jul 31, 2026, 12:27 UTC
started
Jul 31, 2026, 13:26 UTC
resolved
58 min
duration
Minor
impact

Affected components

  • API Gateway
  • Database
  1. resolvedJul 31, 2026, 13:26 UTC

    The incident has been resolved.

  2. monitoringJul 31, 2026, 12:55 UTC

    The upstream DNS provider has implemented a fix and is monitoring the results. We are seeing signs of recovery; we will continue to monitor the situation and will provide further updates as more information becomes available.

  3. identifiedJul 31, 2026, 12:41 UTC

    We have identified that the issue is with an upstream DNS provider, causing DNS creation delays for newly created, unpaused, or updated databases. Our team is actively monitoring the situation and will provide further updates as more information becomes available.

  4. investigatingJul 31, 2026, 12:27 UTC

    We're investigating issues updating DNS records for newly created, unpaused, or updated databases.

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

Supabase incident on Jul 31, 2026: DNS creation delays · APIStatus.watch