Entri is a DNS and domain management platform built for SaaS companies. Incident history and uptime data reflect the performance of our core infrastructure and partner integrations. For API documentation and integration guides, visit our developer docs at https://developers.entri.com.
.shop resolution has been stable since [HH:MM] UTC. The incident was caused by an issue at the .shop registry (GMO Registry), which returned "domain does not exist" responses for .shop domains between roughly 16:18 UTC and [HH:MM] UTC. No DNS records managed through Entri were changed or lost. Any Entri Monitor alerts for .shop domains during this window can be safely ignored, and affected domains will return to a healthy status on the next check. If you still see a .shop domain failing to verify, reach out to support and we'll take a look.
Resolved
.shop resolution has been stable since [HH:MM] UTC. The incident was caused by an issue at the .shop registry (GMO Registry), which returned "domain does not exist" responses for .shop domains between roughly 16:18 UTC and [HH:MM] UTC. No DNS records managed through Entri were changed or lost. Any Entri Monitor alerts for .shop domains during this window can be safely ignored, and affected domains will return to a healthy status on the next check. If you still see a .shop domain failing to verify, reach out to support and we'll take a look.
Monitoring
The .shop registry's nameservers are responding normally again and .shop domains are resolving. Some resolvers may still have the failed answer cached, so a few users could see errors for a little longer. We'll keep monitoring and re-run propagation checks for any .shop domains that were affected.
Identified
We're seeing intermittent DNS resolution failures for domains under the .shop extension. The issue is at the .shop registry level (GMO Registry): since around 16:18 UTC, the registry's nameservers have been returning "domain does not exist" for .shop domains, so resolvers can't reach the domain's own DNS provider.
This is not caused by Entri, and the DNS records configured through Entri remain in place at each domain's DNS provider. Nothing has been deleted or changed.
What you might notice while this lasts:
.shop domains, and custom domains that point to a .shop hostname via CNAME, may fail to load or show as not propagated.
Domain connection and verification flows for .shop domains may stall or report records as missing.
Entri Monitor may flag .shop domains as unreachable or report their records as missing, and you may receive alerts for them. These alerts reflect the registry issue, not a real change to your users' DNS configuration.
Other extensions (.com, .io, etc.) are not affected.
There's no action needed on your side or your users' side. Please don't ask users to re-enter or change their DNS records, since the records are correct and will resolve again once the registry is fixed. Registrars have escalated the issue to the registry, and we're monitoring it closely. We'll post an update as soon as we know more.
