DNS response history for ns020-eute04m3tjd9tk1e.e.d-53.jp

ns020-eute04m3tjd9tk1e.e.d-53.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-24. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 158 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 ns020-eute04m3tjd9tk1e.e.d-53.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

158 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.180.146.111

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns020-eute04m3tjd9tk1e.e.d-53.jp

Showing DNS history for 2026-08-24 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
34 2026-08-24 14:05 639231765923559455
106 ms 203.180.146.111
33 2026-08-24 13:48 639231755868832964
109 ms 203.180.146.111
32 2026-08-24 13:31 639231745628278877
71 ms 203.180.146.111
31 2026-08-24 13:14 639231735407682062
99 ms 203.180.146.111
30 2026-08-24 12:21 639231703815441688
44 ms 203.180.146.111
29 2026-08-24 12:05 639231693747052549
100 ms 203.180.146.111
28 2026-08-24 11:48 639231683712487276
99 ms 203.180.146.111
27 2026-08-24 11:31 639231673513573868
102 ms 203.180.146.111
26 2026-08-24 10:38 639231641791249939
112 ms 203.180.146.111
25 2026-08-24 10:22 639231631866211033
115 ms 203.180.146.111
24 2026-08-24 10:05 639231621644955316
34 ms 203.180.146.111
23 2026-08-24 09:48 639231611478799259
98 ms 203.180.146.111
22 2026-08-24 08:55 639231579923718211
154 ms 203.180.146.111
21 2026-08-24 08:38 639231569810702936
97 ms 203.180.146.111
20 2026-08-24 08:21 639231559762411619
94 ms 203.180.146.111
19 2026-08-24 08:05 639231549663595407
100 ms 203.180.146.111
18 2026-08-24 07:12 639231518076817246
41 ms 203.180.146.111
17 2026-08-24 06:56 639231508078650885
96 ms 203.180.146.111
16 2026-08-24 06:39 639231498210697093
92 ms 203.180.146.111
15 2026-08-24 06:22 639231488109699360
101 ms 203.180.146.111
14 2026-08-24 05:30 639231456772510692
96 ms 203.180.146.111
13 2026-08-24 05:14 639231447084631185
116 ms 203.180.146.111
12 2026-08-24 04:57 639231437208519473
203 ms 203.180.146.111
11 2026-08-24 04:41 639231427209627490
2049 ms 203.180.146.111
10 2026-08-24 03:48 639231395791246644
98 ms 203.180.146.111
9 2026-08-24 03:32 639231386075551458
93 ms 203.180.146.111
8 2026-08-24 03:16 639231376208713791
94 ms 203.180.146.111
7 2026-08-24 02:59 639231366170589276
95 ms 203.180.146.111
6 2026-08-24 02:07 639231334732159368
99 ms 203.180.146.111
5 2026-08-24 01:50 639231325035670078
92 ms 203.180.146.111
4 2026-08-24 01:34 639231315132253837
47 ms 203.180.146.111
3 2026-08-24 01:17 639231305014280808
206 ms 203.180.146.111
2 2026-08-24 00:25 639231273779380675
110 ms 203.180.146.111
1 2026-08-24 00:09 639231264180839154
94 ms 203.180.146.111