Our monitoring started alerting around 00:27 UTC+8 because services using .shop domains could no longer reach their API endpoints. The official .shop website was also unavailable, even though our domain registration is valid through 2027. Queries to the registry's authoritative nameserver returned authoritative NXDOMAIN responses for both the registry website and multiple .shop domains. Has anyone else seen this, and does it look like a broader top-level-domain outage? Service appeared to be partially recovering around 01:17 UTC+8.
3 Answers
This looked like a registry-side DNS problem. The authoritative servers were returning NXDOMAIN, so changing local DNS settings or renewing a domain would not have fixed it. Several sites became reachable again as the registry recovered.
Our site was unreachable too, but it is working normally again now. We did not make any changes, so the recovery seems to have happened upstream rather than through a local fix.
Yes, we saw the same behavior. Internal services using .shop hostnames stopped resolving at roughly 00:27 UTC+8, and the issue appeared to affect multiple domains rather than a single expired registration. It started coming back on its own later.
That matches what we observed—the domains and registration were still active, but authoritative resolution failed temporarily.