DNS response history for ns2.auto-value.jp

ns2.auto-value.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-25. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 509 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.auto-value.jp.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

509 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

168.63.255.33

Most recently resolved hosting IP on selected date

Successful Responses

38

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.auto-value.jp

Showing DNS history for 2026-08-25 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
38 2026-08-25 12:59 639232587225721862
531 ms 168.63.255.33
37 2026-08-25 12:42 639232576780683689
504 ms 168.63.255.33
36 2026-08-25 12:24 639232566381512620
500 ms 168.63.255.33
35 2026-08-25 12:07 639232556111768563
501 ms 168.63.255.33
34 2026-08-25 11:50 639232545839529039
515 ms 168.63.255.33
33 2026-08-25 11:33 639232535349285207
498 ms 168.63.255.33
32 2026-08-25 11:15 639232524938080723
506 ms 168.63.255.33
31 2026-08-25 10:22 639232492740373468
497 ms 168.63.255.33
30 2026-08-25 10:04 639232482235303141
498 ms 168.63.255.33
29 2026-08-25 09:47 639232471861770303
495 ms 168.63.255.33
28 2026-08-25 09:30 639232461630217327
521 ms 168.63.255.33
27 2026-08-25 09:12 639232451282965990
502 ms 168.63.255.33
26 2026-08-25 08:55 639232440814614938
504 ms 168.63.255.33
25 2026-08-25 08:38 639232430410720425
487 ms 168.63.255.33
24 2026-08-25 08:20 639232420003096185
489 ms 168.63.255.33
23 2026-08-25 08:03 639232409467287444
502 ms 168.63.255.33
22 2026-08-25 07:46 639232399077195997
527 ms 168.63.255.33
21 2026-08-25 07:28 639232388731528337
488 ms 168.63.255.33
20 2026-08-25 07:11 639232378288598612
540 ms 168.63.255.33
19 2026-08-25 06:17 639232346196373643
504 ms 168.63.255.33
18 2026-08-25 06:00 639232336112370741
501 ms 168.63.255.33
17 2026-08-25 05:44 639232326146508970
492 ms 168.63.255.33
16 2026-08-25 05:27 639232316189381720
496 ms 168.63.255.33
15 2026-08-25 05:10 639232306217998913
494 ms 168.63.255.33
14 2026-08-25 04:54 639232296255744174
496 ms 168.63.255.33
13 2026-08-25 04:37 639232286095760789
509 ms 168.63.255.33
12 2026-08-25 04:20 639232276086186273
491 ms 168.63.255.33
11 2026-08-25 04:03 639232265900986425
492 ms 168.63.255.33
10 2026-08-25 03:47 639232255723518075
510 ms 168.63.255.33
9 2026-08-25 03:29 639232245484452890
765 ms 168.63.255.33
8 2026-08-25 03:12 639232235157175331
494 ms 168.63.255.33
7 2026-08-25 02:19 639232203197189095
491 ms 168.63.255.33
6 2026-08-25 02:02 639232192844564298
524 ms 168.63.255.33
5 2026-08-25 01:45 639232182496008942
495 ms 168.63.255.33
4 2026-08-25 01:27 639232172197053132
504 ms 168.63.255.33
3 2026-08-25 00:34 639232140250307418
490 ms 168.63.255.33
2 2026-08-25 00:17 639232129927860324
494 ms 168.63.255.33
1 2026-08-25 00:00 639232119551972438
502 ms 168.63.255.33