DNS response history for ns2.highclay.co.jp

ns2.highclay.co.jp 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 34 DNS check records, 34 successful responses, 0 failed responses, and 560 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 ns2.highclay.co.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

560 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

160.251.152.112

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns2.highclay.co.jp

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
34 2026-08-26 10:45 639233370841350248
541 ms 160.251.152.112
33 2026-08-26 10:28 639233360361507238
558 ms 160.251.152.112
32 2026-08-26 10:10 639233350067824371
273 ms 160.251.152.112
31 2026-08-26 09:53 639233339545274518
559 ms 160.251.152.112
30 2026-08-26 09:36 639233329214918079
573 ms 160.251.152.112
29 2026-08-26 09:18 639233318749762337
537 ms 160.251.152.112
28 2026-08-26 09:01 639233308387917838
1082 ms 160.251.152.112
27 2026-08-26 08:44 639233297961740122
1079 ms 160.251.152.112
26 2026-08-26 08:26 639233287487159094
3 ms 160.251.152.112
25 2026-08-26 08:09 639233276995531707
278 ms 160.251.152.112
24 2026-08-26 07:51 639233266521568229
556 ms 160.251.152.112
23 2026-08-26 07:34 639233256081047431
277 ms 160.251.152.112
22 2026-08-26 06:40 639233223620132921
553 ms 160.251.152.112
21 2026-08-26 06:22 639233213287814244
4 ms 160.251.152.112
20 2026-08-26 06:05 639233202925983161
560 ms 160.251.152.112
19 2026-08-26 05:48 639233192644780696
540 ms 160.251.152.112
18 2026-08-26 05:31 639233182401183833
557 ms 160.251.152.112
17 2026-08-26 05:14 639233172074181051
2 ms 160.251.152.112
16 2026-08-26 04:56 639233161808421455
4 ms 160.251.152.112
15 2026-08-26 04:39 639233151357344052
546 ms 160.251.152.112
14 2026-08-26 04:22 639233141034116946
1339 ms 160.251.152.112
13 2026-08-26 04:05 639233130828334142
269 ms 160.251.152.112
12 2026-08-26 03:48 639233120373450007
529 ms 160.251.152.112
11 2026-08-26 03:30 639233110066216193
270 ms 160.251.152.112
10 2026-08-26 02:37 639233078065410564
1088 ms 160.251.152.112
9 2026-08-26 02:20 639233067787457832
548 ms 160.251.152.112
8 2026-08-26 02:03 639233057501801162
2267 ms 160.251.152.112
7 2026-08-26 01:46 639233047089431703
277 ms 160.251.152.112
6 2026-08-26 01:28 639233036754790688
543 ms 160.251.152.112
5 2026-08-26 01:11 639233026412602472
556 ms 160.251.152.112
4 2026-08-26 00:54 639233016064066127
635 ms 160.251.152.112
3 2026-08-26 00:37 639233005922655772
551 ms 160.251.152.112
2 2026-08-26 00:20 639232995672256907
555 ms 160.251.152.112
1 2026-08-26 00:02 639232985300872416
526 ms 160.251.152.112