We started checking Name.com on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Name.com reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Name.com's own status page declared. Below it, any public chatter we saw about Name.com and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Name.com's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Name.com in the last 24 hours, which is not evidence that nothing is wrong.
Name.com's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Name.com's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Name.com next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
447
US-West
99.71%
344
Europe
99.68%
315
Asia-Pacific
100.00%
192
Their declared record
Name.com's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Incident Root Cause Analysis: Oct 31, 2026 DNS ChangesOngoing, all systems operational
Nov 3, 2026, 8:33 PM UTC, open for 1d 21h so farmonitoring
their latest update (Nov 3, 2026, 8:33 PM 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/f…
Incident Root Cause Analysis: Oct 31, 2026 DNS ChangesAll systems operational
Nov 3, 2026, 8:28 PM UTCmonitoring
their latest update (Nov 3, 2026, 8:28 PM 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: [Root Cause Analysis](http…
Degraded Performance - .si Registry ConnectionAll systems operational
Oct 1, 2026, 3:20 PM UTC to Nov 3, 2026, 5:49 PM UTC (33d 2h)resolved
their latest update (Nov 3, 2026, 5:49 PM UTC): This incident has been resolved.
Service degradation (api.name.com, www.name.com)All systems operational
Jul 24, 2026, 1:04 PM UTC to Jul 24, 2026, 1:09 PM UTC (5 min)resolved
their latest update (Jul 24, 2026, 1:09 PM UTC): This incident has been resolved.
Identity Digital - Domain Create and Renewal ErrorsMinor incident
Jul 11, 2026, 7:00 PM UTC to Jul 11, 2026, 7:00 PM UTC (0 min)resolved
their latest update (Jul 11, 2026, 7:00 PM UTC): Between 1:01 PM and 1:19 PM MT (19:01–19:19 UTC), we were experiencing errors on registrations and renewals for TLDs operated by Identity Digital. The issue has been resolved, and registrations and renewals are now processing normally.
We apologize for any inconvenience this may…
DENIC DNS Disruption - DNSSEC outage .DEPartial outage
May 5, 2026, 10:01 PM UTC to May 6, 2026, 12:07 AM UTC (2h 6m)resolved
their latest update (May 6, 2026, 12:07 AM UTC): This incident has been resolved. DENIC confirmed systems are operating normally again for .de domains, but are still investigating the cause of the temporary disruption. For a posted summary directly from DENIC, follow their status page here https://status.denic.de/.
API outageMajor outage
Apr 29, 2026, 3:03 PM UTC to Apr 29, 2026, 4:32 PM UTC (1h 29m)postmortem published
their latest update (May 8, 2026, 3:29 PM UTC): * **Duration:** 14:33 UTC – 16:09 UTC \(~96 minutes\)
* **Impact:** The [api.name.com](http://api.name.com) endpoint was unreachable to external clients, resulting in socket timeouts and 502 errors.
* **Root Cause Summary:** The outage was triggered by an unanticipated 50x surge …
Website and API OutagePartial outage
Nov 18, 2025, 3:43 PM UTC to Nov 18, 2025, 3:43 PM UTC (0 min)resolved
their latest update (Nov 18, 2025, 3:43 PM UTC): After an interruption to www.name.com and api.name.com, service was restored at approximately 2:22pm UTC. We are continuing to monitor to ensure continued stability.
.Space DNS resolution degradedMaintenance
Sep 24, 2025, 3:32 PM UTC to Sep 25, 2025, 4:06 PM UTC (1d 0h)resolved
their latest update (Sep 25, 2025, 4:06 PM UTC): This incident has been resolved.
These entries are Name.com's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Name.com's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.