At around 9AM UTC we began to see signs that name.com services were having problems at the DNS level, with some websites using this DNS service becoming unavailable intermittently and others longer term with at this point up to 5 hours of downtime logged.

At this stage name.com has not updated their Status Page to explain the issue to users - https://status.name.com/

We expect some users of this server to receive valid outage reports that will be replicable from browser and terminal in the regions they are reported in. We are seeing these errors expressed as "Domain not found" and "Timeout/connection refused" where name.com DNS was either unable to respond to a request within a reasonable amount of time, or provided an empty or invalid response.

We will post any further updates here as the situation develops.