DNS response history for ns20.iodata.jp

ns20.iodata.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-26. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 467 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 ns20.iodata.jp.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

467 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.121.197.105

Most recently resolved hosting IP on selected date

Successful Responses

26

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 ns20.iodata.jp

Showing DNS history for 2026-08-26 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
26 2026-08-26 08:26 639233287487159094
556 ms 211.121.197.105
25 2026-08-26 08:08 639233276995531707
567 ms 211.121.197.105
24 2026-08-26 07:51 639233266521568229
557 ms 211.121.197.105
23 2026-08-26 07:33 639233256081047431
554 ms 211.121.197.105
22 2026-08-26 06:39 639233223620132921
264 ms 211.121.197.105
21 2026-08-26 06:22 639233213287814244
573 ms 211.121.197.105
20 2026-08-26 06:05 639233202925983161
282 ms 211.121.197.105
19 2026-08-26 05:47 639233192644780696
544 ms 211.121.197.105
18 2026-08-26 05:30 639233182401183833
262 ms 211.121.197.105
17 2026-08-26 05:13 639233172074181051
290 ms 211.121.197.105
16 2026-08-26 04:56 639233161808421455
570 ms 211.121.197.105
15 2026-08-26 04:39 639233151357344052
267 ms 211.121.197.105
14 2026-08-26 04:21 639233141034116946
553 ms 211.121.197.105
13 2026-08-26 04:04 639233130828334142
658 ms 211.121.197.105
12 2026-08-26 03:47 639233120373450007
587 ms 211.121.197.105
11 2026-08-26 03:30 639233110066216193
580 ms 211.121.197.105
10 2026-08-26 02:37 639233078065410564
376 ms 211.121.197.105
9 2026-08-26 02:19 639233067787457832
545 ms 211.121.197.105
8 2026-08-26 02:02 639233057501801162
555 ms 211.121.197.105
7 2026-08-26 01:45 639233047089431703
540 ms 211.121.197.105
6 2026-08-26 01:28 639233036754790688
31 ms 211.121.197.105
5 2026-08-26 01:11 639233026412602472
532 ms 211.121.197.105
4 2026-08-26 00:53 639233016064066127
541 ms 211.121.197.105
3 2026-08-26 00:36 639233005922655772
553 ms 211.121.197.105
2 2026-08-26 00:19 639232995672256907
541 ms 211.121.197.105
1 2026-08-26 00:02 639232985300872416
267 ms 211.121.197.105