← Back to Supabase History
major✓ Resolved

Reports of DNS lookup errors for some customers in the United States

SupabaseThu, Feb 5, 2026, 01:52 AM
Status
resolved
Duration
4h 57m
Updates
5
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedThu, Feb 5, 2026, 06:50 AM
This incident has been resolved.
monitoringThu, Feb 5, 2026, 03:48 AM
Our upstream provider has pushed a fix, and requests seem to be back to normal now. According to data from our partner, users in the US South were largely affected, with users in and around Texas being the most common, but some users in and around Georgia may have also seen issues, but these should all be resolved at this point. Users connecting to project URLs should no longer be seeing "DNS address could not be found" errors. We are continuing to monitor the situation.
identifiedThu, Feb 5, 2026, 03:22 AM
Our upstream provider has identified the specifc issues with DNS resolution and has begun working on a fix. Projects and the underlying infrastructure are unaffected, and remain running and available for users without affected DNS Providers. Affected users will see errors similar to "DNS address could not be found"
identifiedThu, Feb 5, 2026, 03:03 AM
We are continuing to work on this with our upstream network provider. Projects and the underlying infrastructure are unaffected, and remain running and available for users without affected DNS Providers. Affected users will see errors similar to "DNS address could not be found"
identifiedThu, Feb 5, 2026, 02:21 AM
Our upstream network provider has identified an issue and is working on a fix. Projects and the underlying infrastructure are unaffected, and remain running and available for users without affected DNS Providers. Affected users will see errors similar to "DNS address could not be found"
investigatingThu, Feb 5, 2026, 01:52 AM
We are seeing reports of DNS Lookup failures for users based in the United States. The issue does not seem to affect all DNS providers, and we are still working to narrow down affected areas. Projects and the underlying infrastructure are unaffected, and remain running and available for users without affected DNS Providers. Affected users will see errors similar to "DNS address could not be found"

📊 TECHNICAL DETAILS

Internal ID
f3a019bc-60e3-4c45-acd2-d23cf198d3a4
External ID
9t3fvctpj1hq
🕐 Started
Thu, Feb 5, 2026, 01:52 AM
🔄 Last Updated
Thu, Feb 5, 2026, 06:50 AM
✓ Resolved
Thu, Feb 5, 2026, 06:50 AM
MAJOR
Impact Level
4h 57m
Total Duration
5
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed