Is Name.com down?
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 passingchecked 4 minutes ago
Our checks of Name.com pass from all 4 regions we check.
As of Nov 5, 2026, 3:03 PM UTC, RealUptime's checks of Name.com passed in all 4 regions that returned a reading.
Name.com reports: All systems operational (“All Systems Operational”)
Name.com reports an active incident: Incident Root Cause Analysis: Oct 31, 2026 DNS Changes (all systems operational, since Nov 3, 2026, 8:33 PM UTC). Their summary currently reads “All systems operational” even so: the summary and the incident come from two separately polled feeds and can disagree.
Name.com's own component breakdown, as they publish it
- name.com WebsiteOperational
- name.com APIOperational
- name.com Registry ConnectionsOperational
These are Name.com's components, named and scored by Name.com. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is Name.com's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Name.com response time, by region
Check your own site while you wait on Name.com
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Name.com. It cannot diagnose Name.com's own systems.
Email me when Name.com reports an incident on its status page, and again when it reports it resolved.
Get an email when Name.com reports an incident
Email me when Name.com reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaNot monitored from this regionUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 1025msstatus code: 200checked: Nov 5, 2026, 3:00 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Name.com normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 950msstatus code: 200checked: Nov 5, 2026, 3:00 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Name.com normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralNot monitored from this regionName.com is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- CanadaNot monitored from this regionName.com is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- South AmericaNot monitored from this regionName.com is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- EuropeNot monitored from this regionEurope, UK
- EuropeChecks passinglatency: 460msstatus code: 200checked: Nov 5, 2026, 2:57 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Name.com normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKNot monitored from this regionName.com is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- Asia PacificNot monitored from this regionAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 1408msstatus code: 200checked: Nov 5, 2026, 3:03 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Name.com normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaNot monitored from this regionName.com is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- AustraliaNot monitored from this regionName.com is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Name.com, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Name.com yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Name.com since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Name.com covering any window you pick, with our check readings and Name.com's own claim at the time, side by side.
Full check history for Name.com: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
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
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/name-com)<a href="https://realuptime.io/outages/name-com"><img src="https://realuptime.io/outages/name-com/badge.svg?days=30" alt="Name.com uptime by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is Name.com down?", https://realuptime.io/outages/name-com. The readings change with every check, so give the date you read them.
What we check
What our check can and cannot see
A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.
Host checked: www.name.com