DNS response history for ns2.ml-club.jp

ns2.ml-club.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 32 DNS check records, 32 successful responses, 0 failed responses, and 595 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.ml-club.jp.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

595 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

124.33.135.130

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 ns2.ml-club.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
32 2026-08-25 11:15 639232524938080723
1517 ms 124.33.135.130
31 2026-08-25 10:22 639232492740373468
3 ms 124.33.135.130
30 2026-08-25 10:04 639232482235303141
4 ms 124.33.135.130
29 2026-08-25 09:47 639232471861770303
1088 ms 124.33.135.130
28 2026-08-25 09:30 639232461630217327
6 ms 124.33.135.130
27 2026-08-25 09:13 639232451282965990
10 ms 124.33.135.130
26 2026-08-25 08:55 639232440814614938
1624 ms 124.33.135.130
25 2026-08-25 08:38 639232430410720425
4 ms 124.33.135.130
24 2026-08-25 08:21 639232420003096185
2 ms 124.33.135.130
23 2026-08-25 08:03 639232409467287444
259 ms 124.33.135.130
22 2026-08-25 07:46 639232399077195997
759 ms 124.33.135.130
21 2026-08-25 07:28 639232388731528337
1431 ms 124.33.135.130
20 2026-08-25 07:11 639232378288598612
262 ms 124.33.135.130
19 2026-08-25 06:17 639232346196373643
1493 ms 124.33.135.130
18 2026-08-25 06:00 639232336112370741
10 ms 124.33.135.130
17 2026-08-25 05:44 639232326146508970
4 ms 124.33.135.130
16 2026-08-25 05:27 639232316189381720
10 ms 124.33.135.130
15 2026-08-25 05:11 639232306217998913
3 ms 124.33.135.130
14 2026-08-25 04:54 639232296255744174
1073 ms 124.33.135.130
13 2026-08-25 04:37 639232286095760789
358 ms 124.33.135.130
12 2026-08-25 04:20 639232276086186273
2 ms 124.33.135.130
11 2026-08-25 04:03 639232265900986425
1077 ms 124.33.135.130
10 2026-08-25 03:47 639232255723518075
3854 ms 124.33.135.130
9 2026-08-25 03:29 639232245484452890
266 ms 124.33.135.130
8 2026-08-25 03:12 639232235157175331
3 ms 124.33.135.130
7 2026-08-25 02:19 639232203197189095
1034 ms 124.33.135.130
6 2026-08-25 02:02 639232192844564298
13 ms 124.33.135.130
5 2026-08-25 01:45 639232182496008942
2 ms 124.33.135.130
4 2026-08-25 01:27 639232172197053132
2 ms 124.33.135.130
3 2026-08-25 00:34 639232140250307418
1430 ms 124.33.135.130
2 2026-08-25 00:17 639232129927860324
1440 ms 124.33.135.130
1 2026-08-25 00:00 639232119551972438
3 ms 124.33.135.130