DNS response history for ns1.topducks.com

ns1.topducks.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 34 DNS check records, 33 successful responses, 1 failed responses, and 114 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 ns1.topducks.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

114 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

108.160.157.7

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns1.topducks.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
34 2026-08-24 14:05 639231765923559455
248 ms 108.160.157.7
33 2026-08-24 13:48 639231755868832964
114 ms 108.160.157.7
32 2026-08-24 13:31 639231745628278877
116 ms 108.160.157.7
31 2026-08-24 13:14 639231735407682062
249 ms 108.160.157.7
30 2026-08-24 12:21 639231703815441688
8 ms 108.160.157.7
29 2026-08-24 12:05 639231693747052549
11 ms 108.160.157.7
28 2026-08-24 11:48 639231683712487276
118 ms 108.160.157.7
27 2026-08-24 11:31 639231673513573868
250 ms 108.160.157.7
26 2026-08-24 10:38 639231641791249939
129 ms 108.160.157.7
25 2026-08-24 10:22 639231631866211033
130 ms 108.160.157.7
24 2026-08-24 10:05 639231621644955316
151 ms 108.160.157.7
23 2026-08-24 09:48 639231611478799259
13 ms 108.160.157.7
22 2026-08-24 08:55 639231579923718211
8 ms 108.160.157.7
21 2026-08-24 08:38 639231569810702936
247 ms 108.160.157.7
20 2026-08-24 08:21 639231559762411619
4 ms 108.160.157.7
19 2026-08-24 08:05 639231549663595407
232 ms 108.160.157.7
18 2026-08-24 07:12 639231518076817246
7 ms 108.160.157.7
17 2026-08-24 06:56 639231508078650885
233 ms 108.160.157.7
16 2026-08-24 06:39 639231498210697093
229 ms 108.160.157.7
15 2026-08-24 06:22 639231488109699360
5 ms 108.160.157.7
14 2026-08-24 05:30 639231456772510692
148 ms 108.160.157.7
13 2026-08-24 05:14 639231447084631185
4 ms 108.160.157.7
12 2026-08-24 04:57 639231437208519473
254 ms 108.160.157.7
11 2026-08-24 04:41 639231427209627490
2 ms 108.160.157.7
10 2026-08-24 03:48 639231395791246644
233 ms 108.160.157.7
9 2026-08-24 03:32 639231386075551458
249 ms 108.160.157.7
8 2026-08-24 03:16 639231376208713791
144 ms 108.160.157.7
7 2026-08-24 02:59 639231366170589276
187 ms 108.160.157.7
6 2026-08-24 02:07 639231334732159368
2 ms 108.160.157.7
5 2026-08-24 01:50 639231325035670078
3 ms 108.160.157.7
4 2026-08-24 01:34 639231315132253837
-
3 2026-08-24 01:17 639231305014280808
2 ms 108.160.157.7
2 2026-08-24 00:25 639231273779380675
22 ms 108.160.157.7
1 2026-08-24 00:09 639231264180839154
3 ms 108.160.157.7