Our monitoring alerted us overnight that several systems could no longer reach API endpoints hosted under .shop domains. The official .shop registry website also became unreachable. The domain itself is active and paid through 2027, so expiration was not the issue. During the incident, queries such as `dig get.shop @a.gmoregistry.net` and queries for other .shop domains returned authoritative NXDOMAIN responses. The outage appeared to begin around 00:27 UTC+8 and showed signs of partial recovery by approximately 01:17 UTC+8. Is anyone else seeing the same behavior, and was there an explanation for the incident?
2 Answers
The outage appeared to be recovering on its own. Several previously unreachable sites started resolving again without any configuration changes, and other reports indicated the same partial recovery. There does not seem to have been a client-side fix; the authoritative DNS service was likely restored upstream.
We saw the same failure starting at roughly 00:27 UTC+8. Internal services using .shop names stopped resolving, and direct queries to the registry’s authoritative servers returned NXDOMAIN. It affected more than one domain, so this looked like a registry or authoritative DNS problem rather than an individual domain renewal issue.
That matches our experience. The site became reachable again without changing our DNS settings or renewing the domain.