DNS response history for ns01.hpc.tokyo

ns01.hpc.tokyo is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-26. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 532 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns01.hpc.tokyo.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

532 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.17.233.197

Most recently resolved hosting IP on selected date

Successful Responses

26

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns01.hpc.tokyo

Showing DNS history for 2026-08-26 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
26 2026-08-26 08:26 639233287487159094
259 ms 211.17.233.197
25 2026-08-26 08:09 639233276995531707
530 ms 211.17.233.197
24 2026-08-26 07:51 639233266521568229
522 ms 211.17.233.197
23 2026-08-26 07:34 639233256081047431
556 ms 211.17.233.197
22 2026-08-26 06:40 639233223620132921
541 ms 211.17.233.197
21 2026-08-26 06:23 639233213287814244
534 ms 211.17.233.197
20 2026-08-26 06:05 639233202925983161
260 ms 211.17.233.197
19 2026-08-26 05:48 639233192644780696
529 ms 211.17.233.197
18 2026-08-26 05:31 639233182401183833
524 ms 211.17.233.197
17 2026-08-26 05:14 639233172074181051
552 ms 211.17.233.197
16 2026-08-26 04:57 639233161808421455
542 ms 211.17.233.197
15 2026-08-26 04:40 639233151357344052
532 ms 211.17.233.197
14 2026-08-26 04:22 639233141034116946
541 ms 211.17.233.197
13 2026-08-26 04:05 639233130828334142
550 ms 211.17.233.197
12 2026-08-26 03:48 639233120373450007
540 ms 211.17.233.197
11 2026-08-26 03:31 639233110066216193
251 ms 211.17.233.197
10 2026-08-26 02:37 639233078065410564
517 ms 211.17.233.197
9 2026-08-26 02:20 639233067787457832
255 ms 211.17.233.197
8 2026-08-26 02:03 639233057501801162
257 ms 211.17.233.197
7 2026-08-26 01:46 639233047089431703
252 ms 211.17.233.197
6 2026-08-26 01:28 639233036754790688
551 ms 211.17.233.197
5 2026-08-26 01:11 639233026412602472
256 ms 211.17.233.197
4 2026-08-26 00:54 639233016064066127
530 ms 211.17.233.197
3 2026-08-26 00:37 639233005922655772
549 ms 211.17.233.197
2 2026-08-26 00:20 639232995672256907
558 ms 211.17.233.197
1 2026-08-26 00:03 639232985300872416
2356 ms 211.17.233.197