DNS response history for ns8.leosv.jp

ns8.leosv.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 29 DNS check records, 29 successful responses, 0 failed responses, and 505 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 ns8.leosv.jp.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

505 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

180.147.239.17

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns8.leosv.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
29 2026-08-25 10:04 639232482235303141
248 ms 180.147.239.17
28 2026-08-25 09:46 639232471861770303
393 ms 180.147.239.17
27 2026-08-25 09:29 639232461630217327
446 ms 180.147.239.17
26 2026-08-25 09:12 639232451282965990
421 ms 180.147.239.17
25 2026-08-25 08:55 639232440814614938
387 ms 180.147.239.17
24 2026-08-25 08:37 639232430410720425
430 ms 180.147.239.17
23 2026-08-25 08:20 639232420003096185
447 ms 180.147.239.17
22 2026-08-25 08:03 639232409467287444
247 ms 180.147.239.17
21 2026-08-25 07:45 639232399077195997
503 ms 180.147.239.17
20 2026-08-25 07:28 639232388731528337
242 ms 180.147.239.17
19 2026-08-25 07:10 639232378288598612
2355 ms 180.147.239.17
18 2026-08-25 06:17 639232346196373643
321 ms 180.147.239.17
17 2026-08-25 06:00 639232336112370741
989 ms 180.147.239.17
16 2026-08-25 05:43 639232326146508970
240 ms 180.147.239.17
15 2026-08-25 05:26 639232316189381720
676 ms 180.147.239.17
14 2026-08-25 05:10 639232306217998913
248 ms 180.147.239.17
13 2026-08-25 04:53 639232296255744174
437 ms 180.147.239.17
12 2026-08-25 04:37 639232286095760789
254 ms 180.147.239.17
11 2026-08-25 04:20 639232276086186273
498 ms 180.147.239.17
10 2026-08-25 04:03 639232265900986425
248 ms 180.147.239.17
9 2026-08-25 03:46 639232255723518075
505 ms 180.147.239.17
8 2026-08-25 03:29 639232245484452890
493 ms 180.147.239.17
7 2026-08-25 03:12 639232235157175331
637 ms 180.147.239.17
6 2026-08-25 02:18 639232203197189095
482 ms 180.147.239.17
5 2026-08-25 02:01 639232192844564298
760 ms 180.147.239.17
4 2026-08-25 01:44 639232182496008942
417 ms 180.147.239.17
3 2026-08-25 01:27 639232172197053132
679 ms 180.147.239.17
2 2026-08-25 00:33 639232140250307418
238 ms 180.147.239.17
1 2026-08-25 00:17 639232129927860324
394 ms 180.147.239.17