Skip to content

Outage tracker / Name.com / In Japan

Is Name.com down in Japan?

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

Name.com's status page

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 Japan, measured from Tokyo

Our Tokyo probe last checked Name.com at Nov 5, 2026, 9:16 PM UTC and read checks passing.

Over the last 24 hours we completed 60 checks from Tokyo and 60 answered cleanly, 100.00% availability.

Of the 3 other regions we check Name.com from, all 3 read checks passing right now.

Email me when Name.com reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Name.com's own statement from its status page, with our regional reading beside it.

What our Tokyo probe measured

TokyoChecks passing60 checks in 24h, 100.00%

Last checked Nov 5, 2026, 9:16 PM UTC.

Name.com from Tokyo over the last 30 days

Over the last 30 days, Name.com answered our Tokyo probe in 1,371 ms on average, and 1 check in 20 took longer than 2,085 ms.

Ranked by average response time across the 4 cities we check Name.com from, Tokyo 4th; Frankfurt was fastest at 493 ms and Tokyo slowest at 1,371 ms.

From Tokyo we ran 201 checks of Name.com in 4 days, and 201 answered cleanly: 100.00% availability.

Every one of those days was clean: not one failed check.

In Tokyo local time (GMT+9), Name.com was slowest around 6 PM, at 1,848 ms on average over the last 14 days, and quickest around 10 PM, at 1,038 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 554100.00%1,411 ms
Wed, Nov 459100.00%1,396 ms
Tue, Nov 361100.00%1,273 ms
Mon, Nov 227100.00%1,463 ms

Name.com outages measured from Japan

Our Tokyo probe measured no confirmed Name.com outage in the last 90 days.

How the other regions read right now

Of the 3 other regions we check Name.com from, all 3 read checks passing right now.

Probe cityRight nowLast 24h
AshburnChecks passing100.00% of 141 checks
San JoseChecks passing100.00% of 110 checks
FrankfurtChecks passing100.00% of 98 checks

Other countries we check Name.com from

How we measured this

Japan readings on this page come from RealUptime's own Tokyo probe 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.

Japan 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 Tokyo

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 servers

Run 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