DNS response history for ns2.ismo.jp

ns2.ismo.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 36 DNS check records, 36 successful responses, 0 failed responses, and 469 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.ismo.jp.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

469 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.160.238.19

Most recently resolved hosting IP on selected date

Successful Responses

36

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.ismo.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
36 2026-08-25 12:41 639232576780683689
310 ms 210.160.238.19
35 2026-08-25 12:23 639232566381512620
241 ms 210.160.238.19
34 2026-08-25 12:06 639232556111768563
489 ms 210.160.238.19
33 2026-08-25 11:49 639232545839529039
246 ms 210.160.238.19
32 2026-08-25 11:32 639232535349285207
247 ms 210.160.238.19
31 2026-08-25 11:14 639232524938080723
489 ms 210.160.238.19
30 2026-08-25 10:20 639232492740373468
245 ms 210.160.238.19
29 2026-08-25 10:03 639232482235303141
2306 ms 210.160.238.19
28 2026-08-25 09:46 639232471861770303
495 ms 210.160.238.19
27 2026-08-25 09:29 639232461630217327
476 ms 210.160.238.19
26 2026-08-25 09:11 639232451282965990
569 ms 210.160.238.19
25 2026-08-25 08:54 639232440814614938
622 ms 210.160.238.19
24 2026-08-25 08:37 639232430410720425
237 ms 210.160.238.19
23 2026-08-25 08:19 639232420003096185
259 ms 210.160.238.19
22 2026-08-25 08:02 639232409467287444
495 ms 210.160.238.19
21 2026-08-25 07:44 639232399077195997
238 ms 210.160.238.19
20 2026-08-25 07:27 639232388731528337
245 ms 210.160.238.19
19 2026-08-25 07:10 639232378288598612
582 ms 210.160.238.19
18 2026-08-25 06:16 639232346196373643
315 ms 210.160.238.19
17 2026-08-25 05:59 639232336112370741
495 ms 210.160.238.19
16 2026-08-25 05:43 639232326146508970
492 ms 210.160.238.19
15 2026-08-25 05:26 639232316189381720
33 ms 210.160.238.19
14 2026-08-25 05:09 639232306217998913
13 ms 210.160.238.19
13 2026-08-25 04:53 639232296255744174
242 ms 210.160.238.19
12 2026-08-25 04:36 639232286095760789
247 ms 210.160.238.19
11 2026-08-25 04:19 639232276086186273
4 ms 210.160.238.19
10 2026-08-25 04:02 639232265900986425
3 ms 210.160.238.19
9 2026-08-25 03:45 639232255723518075
32 ms 210.160.238.19
8 2026-08-25 03:28 639232245484452890
245 ms 210.160.238.19
7 2026-08-25 03:11 639232235157175331
495 ms 210.160.238.19
6 2026-08-25 02:18 639232203197189095
476 ms 210.160.238.19
5 2026-08-25 02:01 639232192844564298
537 ms 210.160.238.19
4 2026-08-25 01:43 639232182496008942
2343 ms 210.160.238.19
3 2026-08-25 01:26 639232172197053132
1157 ms 210.160.238.19
2 2026-08-25 00:33 639232140250307418
484 ms 210.160.238.19
1 2026-08-25 00:16 639232129927860324
486 ms 210.160.238.19