Supabase reported this minor-impact incident on its official status page on Jul 27, 2026, 20:34 UTC. It was resolved after 2h 2m.
Right now Supabase is degraded. Live Supabase status →
This incident is resolved. DNS creation for new projects has been fixed since 20:35 UTC. Backfill of missing DNS records has been completed at 22:20 UTC. Please contact Support if your project seems impacted by missing DNS records.
All failed DNS creation has been backfilled, and customers should no longer see missing DNS records in their projects. DNS record creation and latency have returned to normal levels. We will continue to monitor before resolving this incident.
We have identified and mitigated the issue that was blocking DNS updates. DNS record creation is succeeding, and latency has returned to normal levels. A subset of projects that encountered provisioning failures during the incident will require DNS records to be backfilled, and we are actively remediating these affected projects.
We have identified the cause of delays in DNS records creation and are actively working on a fix. We will continue to provide updates as things progress.
We are investigating failures in provisioning DNS records for projects, there may be delays in creation of DNS records for new or unpaused projects.
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.
Overlapping incidents aren't necessarily related.
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