DNS response history for ns4.dapperducky.com

ns4.dapperducky.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 33 DNS check records, 33 successful responses, 0 failed responses, and 187 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 ns4.dapperducky.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

187 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.233.56.199

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns4.dapperducky.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
33 2026-08-24 13:45 639231755868832964
54 ms 172.233.56.199
32 2026-08-24 13:28 639231745628278877
43 ms 172.233.56.199
31 2026-08-24 13:11 639231735407682062
49 ms 172.233.56.199
30 2026-08-24 12:18 639231703815441688
137 ms 172.233.56.199
29 2026-08-24 12:01 639231693747052549
105 ms 172.233.56.199
28 2026-08-24 11:45 639231683712487276
41 ms 172.233.56.199
27 2026-08-24 11:28 639231673513573868
41 ms 172.233.56.199
26 2026-08-24 10:35 639231641791249939
46 ms 172.233.56.199
25 2026-08-24 10:18 639231631866211033
2173 ms 172.233.56.199
24 2026-08-24 10:01 639231621644955316
53 ms 172.233.56.199
23 2026-08-24 09:44 639231611478799259
51 ms 172.233.56.199
22 2026-08-24 08:52 639231579923718211
46 ms 172.233.56.199
21 2026-08-24 08:35 639231569810702936
78 ms 172.233.56.199
20 2026-08-24 08:18 639231559762411619
52 ms 172.233.56.199
19 2026-08-24 08:01 639231549663595407
45 ms 172.233.56.199
18 2026-08-24 07:09 639231518076817246
38 ms 172.233.56.199
17 2026-08-24 06:52 639231508078650885
44 ms 172.233.56.199
16 2026-08-24 06:35 639231498210697093
50 ms 172.233.56.199
15 2026-08-24 06:19 639231488109699360
122 ms 172.233.56.199
14 2026-08-24 05:26 639231456772510692
172 ms 172.233.56.199
13 2026-08-24 05:10 639231447084631185
82 ms 172.233.56.199
12 2026-08-24 04:54 639231437208519473
50 ms 172.233.56.199
11 2026-08-24 04:37 639231427209627490
28 ms 172.233.56.199
10 2026-08-24 03:45 639231395791246644
109 ms 172.233.56.199
9 2026-08-24 03:29 639231386075551458
44 ms 172.233.56.199
8 2026-08-24 03:12 639231376208713791
75 ms 172.233.56.199
7 2026-08-24 02:55 639231366170589276
41 ms 172.233.56.199
6 2026-08-24 02:03 639231334732159368
49 ms 172.233.56.199
5 2026-08-24 01:47 639231325035670078
2032 ms 172.233.56.199
4 2026-08-24 01:30 639231315132253837
48 ms 172.233.56.199
3 2026-08-24 01:14 639231305014280808
30 ms 172.233.56.199
2 2026-08-24 00:21 639231273779380675
77 ms 172.233.56.199
1 2026-08-24 00:05 639231264180839154
62 ms 172.233.56.199