Is Name.com down in the US?
Vendor reports an incident, no impactWhat Name.com reports
Name.com reports an incident on its status page: Incident Root Cause Analysis: Oct 31, 2026 DNS Changes.
Impact: no impact. Since 2026-11-03 20:33 UTC.
Latest update, 2026-11-03 20:33 UTC: On Oct 31, 2026 (UTC), unauthorized DNS changes were made to 15 customer domains. All changes were restored by Oct 31, 16:11 UTC, and system access for the account where the changes originated has been fully revoked. Read the full incident report here: https://drive.google.com/file/d/1hUsmik81BR5MlX-gDRvwA4OUUPsbvA58/view
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Name.com at Nov 5, 2026, 6:02 PM UTC.
Over the last 24 hours we completed 252 checks from Ashburn and San Jose and 252 answered cleanly, 100.00% availability.
Of the 2 other regions we check Name.com from, all 2 read checks passing right now.
Email me when Name.com reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 6:02 PM UTC.
Name.com from Ashburn and San Jose over the last 30 days
Over the last 30 days, Name.com answered our Ashburn probe in 873 ms on average, and 1 check in 20 took longer than 1,235 ms.
Over the last 30 days, Name.com answered our San Jose probe in 905 ms on average, and 1 check in 20 took longer than 1,415 ms.
Ranked by average response time across the 4 cities we check Name.com from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 492 ms and Tokyo slowest at 1,364 ms.
From Ashburn and San Jose we ran 791 checks of Name.com in 4 days, and 790 answered cleanly: 99.87% availability.
1 of the 4 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.59% across 247 checks.
In Ashburn local time (EST), Name.com was slowest around 4 PM, at 1,072 ms on average over the last 14 days, and quickest around 10 AM, at 506 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 186 | 100.00% | 884 ms |
| Wed, Nov 4 | 254 | 100.00% | 803 ms |
| Tue, Nov 3 | 247 | 99.59% | 928 ms |
| Mon, Nov 2 | 104 | 100.00% | 1,001 ms |
Name.com outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Name.com outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Name.com from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 99 checks |
| Tokyo | Checks passing | 100.00% of 60 checks |
Other countries we check Name.com from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Name.com's public endpoints. They are not user reports, and they are not Name.com's own status page.
See Name.com's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Name.com has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter