DNS response history for ns2.adepalmotor.com

ns2.adepalmotor.com 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 31 DNS check records, 31 successful responses, 0 failed responses, and 310 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.adepalmotor.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

310 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.56.59.125

Most recently resolved hosting IP on selected date

Successful Responses

31

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.adepalmotor.com

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
31 2026-08-24 13:12 639231735407682062
236 ms 5.56.59.125
30 2026-08-24 12:20 639231703815441688
238 ms 5.56.59.125
29 2026-08-24 12:03 639231693747052549
2092 ms 5.56.59.125
28 2026-08-24 11:46 639231683712487276
110 ms 5.56.59.125
27 2026-08-24 11:29 639231673513573868
78 ms 5.56.59.125
26 2026-08-24 10:36 639231641791249939
240 ms 5.56.59.125
25 2026-08-24 10:20 639231631866211033
43 ms 5.56.59.125
24 2026-08-24 10:03 639231621644955316
240 ms 5.56.59.125
23 2026-08-24 09:46 639231611478799259
240 ms 5.56.59.125
22 2026-08-24 08:53 639231579923718211
52 ms 5.56.59.125
21 2026-08-24 08:37 639231569810702936
37 ms 5.56.59.125
20 2026-08-24 08:20 639231559762411619
33 ms 5.56.59.125
19 2026-08-24 08:03 639231549663595407
51 ms 5.56.59.125
18 2026-08-24 07:10 639231518076817246
247 ms 5.56.59.125
17 2026-08-24 06:54 639231508078650885
168 ms 5.56.59.125
16 2026-08-24 06:37 639231498210697093
39 ms 5.56.59.125
15 2026-08-24 06:21 639231488109699360
2045 ms 5.56.59.125
14 2026-08-24 05:28 639231456772510692
265 ms 5.56.59.125
13 2026-08-24 05:12 639231447084631185
12 ms 5.56.59.125
12 2026-08-24 04:56 639231437208519473
235 ms 5.56.59.125
11 2026-08-24 04:39 639231427209627490
40 ms 5.56.59.125
10 2026-08-24 03:46 639231395791246644
35 ms 5.56.59.125
9 2026-08-24 03:30 639231386075551458
37 ms 5.56.59.125
8 2026-08-24 03:14 639231376208713791
4 ms 5.56.59.125
7 2026-08-24 02:57 639231366170589276
263 ms 5.56.59.125
6 2026-08-24 02:05 639231334732159368
7 ms 5.56.59.125
5 2026-08-24 01:49 639231325035670078
2037 ms 5.56.59.125
4 2026-08-24 01:32 639231315132253837
234 ms 5.56.59.125
3 2026-08-24 01:15 639231305014280808
236 ms 5.56.59.125
2 2026-08-24 00:23 639231273779380675
5 ms 5.56.59.125
1 2026-08-24 00:07 639231264180839154
4 ms 5.56.59.125