DNS response history for ns02.v6dns.jp

ns02.v6dns.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-24. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 491 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 ns02.v6dns.jp.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

491 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.127.14.173

Most recently resolved hosting IP on selected date

Successful Responses

32

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 ns02.v6dns.jp

Showing DNS history for 2026-08-24 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
32 2026-08-24 13:36 639231745628278877
788 ms 153.127.14.173
31 2026-08-24 13:18 639231735407682062
276 ms 153.127.14.173
30 2026-08-24 12:26 639231703815441688
5 ms 153.127.14.173
29 2026-08-24 12:09 639231693747052549
801 ms 153.127.14.173
28 2026-08-24 11:52 639231683712487276
284 ms 153.127.14.173
27 2026-08-24 11:35 639231673513573868
4 ms 153.127.14.173
26 2026-08-24 10:42 639231641791249939
1082 ms 153.127.14.173
25 2026-08-24 10:26 639231631866211033
719 ms 153.127.14.173
24 2026-08-24 10:09 639231621644955316
1208 ms 153.127.14.173
23 2026-08-24 09:52 639231611478799259
292 ms 153.127.14.173
22 2026-08-24 08:59 639231579923718211
255 ms 153.127.14.173
21 2026-08-24 08:43 639231569810702936
24 ms 153.127.14.173
20 2026-08-24 08:25 639231559762411619
1061 ms 153.127.14.173
19 2026-08-24 08:09 639231549663595407
737 ms 153.127.14.173
18 2026-08-24 07:16 639231518076817246
1040 ms 153.127.14.173
17 2026-08-24 07:00 639231508078650885
3 ms 153.127.14.173
16 2026-08-24 06:43 639231498210697093
219 ms 153.127.14.173
15 2026-08-24 06:26 639231488109699360
724 ms 153.127.14.173
14 2026-08-24 05:34 639231456772510692
1140 ms 153.127.14.173
13 2026-08-24 05:18 639231447084631185
2 ms 153.127.14.173
12 2026-08-24 05:01 639231437208519473
3 ms 153.127.14.173
11 2026-08-24 04:45 639231427209627490
2 ms 153.127.14.173
10 2026-08-24 03:52 639231395791246644
219 ms 153.127.14.173
9 2026-08-24 03:36 639231386075551458
293 ms 153.127.14.173
8 2026-08-24 03:20 639231376208713791
3 ms 153.127.14.173
7 2026-08-24 03:03 639231366170589276
3 ms 153.127.14.173
6 2026-08-24 02:11 639231334732159368
246 ms 153.127.14.173
5 2026-08-24 01:54 639231325035670078
1035 ms 153.127.14.173
4 2026-08-24 01:38 639231315132253837
727 ms 153.127.14.173
3 2026-08-24 01:21 639231305014280808
243 ms 153.127.14.173
2 2026-08-24 00:29 639231273779380675
2 ms 153.127.14.173
1 2026-08-24 00:13 639231264180839154
2272 ms 153.127.14.173