Live / Fastly / Incident
Fastly: Domainr: Some Top-level Domains (TLDs) may return an 'unknown' status
Fastly · fastly.comResolved2026-11-12 20:54 UTC
Public — what happened
Summary
Fastly said its Domainr service, which checks domain name availability, had a problem where some top-level domains (the endings such as .com) could come back with an "unknown" status. Customers may have seen unverified or "unknown" results for certain domain endings. Fastly said some registries were affected from 17:16 UTC on October 25 until 18:18 UTC on November 12. On November 12 at 20:54 UTC, Fastly said engineering had confirmed full restoration and marked the incident resolved, without naming a cause.
Timeline
- Started — 2026-10-23 02:20 UTC
- Resolved — 2026-11-12 20:54 UTC · 21 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Fastly against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Fastly: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Fastly report →
More from Fastly
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.