DNS response history for ns014-n6ls50cfkb5ae1mo.n.d-53.jp

ns014-n6ls50cfkb5ae1mo.n.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 29 DNS check records, 28 successful responses, 1 failed responses, and 333 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 ns014-n6ls50cfkb5ae1mo.n.d-53.jp.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

333 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.180.146.105

Most recently resolved hosting IP on selected date

Successful Responses

28

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns014-n6ls50cfkb5ae1mo.n.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
29 2026-08-24 12:03 639231693747052549
76 ms 203.180.146.105
28 2026-08-24 11:46 639231683712487276
36 ms 203.180.146.105
27 2026-08-24 11:29 639231673513573868
771 ms 203.180.146.105
26 2026-08-24 10:36 639231641791249939
116 ms 203.180.146.105
25 2026-08-24 10:19 639231631866211033
149 ms 203.180.146.105
24 2026-08-24 10:03 639231621644955316
20 ms 203.180.146.105
23 2026-08-24 09:46 639231611478799259
107 ms 203.180.146.105
22 2026-08-24 08:53 639231579923718211
80 ms 203.180.146.105
21 2026-08-24 08:36 639231569810702936
58 ms 203.180.146.105
20 2026-08-24 08:19 639231559762411619
92 ms 203.180.146.105
19 2026-08-24 08:03 639231549663595407
38 ms 203.180.146.105
18 2026-08-24 07:10 639231518076817246
98 ms 203.180.146.105
17 2026-08-24 06:54 639231508078650885
94 ms 203.180.146.105
16 2026-08-24 06:37 639231498210697093
49 ms 203.180.146.105
15 2026-08-24 06:20 639231488109699360
275 ms 203.180.146.105
14 2026-08-24 05:28 639231456772510692
100 ms 203.180.146.105
13 2026-08-24 05:12 639231447084631185
-
12 2026-08-24 04:55 639231437208519473
111 ms 203.180.146.105
11 2026-08-24 04:39 639231427209627490
4024 ms 203.180.146.105
10 2026-08-24 03:46 639231395791246644
120 ms 203.180.146.105
9 2026-08-24 03:30 639231386075551458
102 ms 203.180.146.105
8 2026-08-24 03:14 639231376208713791
105 ms 203.180.146.105
7 2026-08-24 02:57 639231366170589276
111 ms 203.180.146.105
6 2026-08-24 02:05 639231334732159368
100 ms 203.180.146.105
5 2026-08-24 01:48 639231325035670078
96 ms 203.180.146.105
4 2026-08-24 01:32 639231315132253837
126 ms 203.180.146.105
3 2026-08-24 01:15 639231305014280808
2065 ms 203.180.146.105
2 2026-08-24 00:23 639231273779380675
120 ms 203.180.146.105
1 2026-08-24 00:07 639231264180839154
91 ms 203.180.146.105