DNS response history for ns20.zaagle.com

ns20.zaagle.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 29 DNS check records, 29 successful responses, 0 failed responses, and 279 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 ns20.zaagle.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

279 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

104.248.205.108

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns20.zaagle.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
29 2026-08-24 12:03 639231693747052549
160 ms 104.248.205.108
28 2026-08-24 11:46 639231683712487276
158 ms 104.248.205.108
27 2026-08-24 11:29 639231673513573868
8 ms 104.248.205.108
26 2026-08-24 10:36 639231641791249939
151 ms 104.248.205.108
25 2026-08-24 10:19 639231631866211033
156 ms 104.248.205.108
24 2026-08-24 10:03 639231621644955316
161 ms 104.248.205.108
23 2026-08-24 09:45 639231611478799259
17 ms 104.248.205.108
22 2026-08-24 08:53 639231579923718211
158 ms 104.248.205.108
21 2026-08-24 08:36 639231569810702936
153 ms 104.248.205.108
20 2026-08-24 08:19 639231559762411619
174 ms 104.248.205.108
19 2026-08-24 08:02 639231549663595407
198 ms 104.248.205.108
18 2026-08-24 07:10 639231518076817246
346 ms 104.248.205.108
17 2026-08-24 06:53 639231508078650885
634 ms 104.248.205.108
16 2026-08-24 06:37 639231498210697093
193 ms 104.248.205.108
15 2026-08-24 06:20 639231488109699360
163 ms 104.248.205.108
14 2026-08-24 05:28 639231456772510692
6 ms 104.248.205.108
13 2026-08-24 05:12 639231447084631185
4 ms 104.248.205.108
12 2026-08-24 04:55 639231437208519473
310 ms 104.248.205.108
11 2026-08-24 04:38 639231427209627490
4 ms 104.248.205.108
10 2026-08-24 03:46 639231395791246644
2033 ms 104.248.205.108
9 2026-08-24 03:30 639231386075551458
295 ms 104.248.205.108
8 2026-08-24 03:14 639231376208713791
3 ms 104.248.205.108
7 2026-08-24 02:57 639231366170589276
160 ms 104.248.205.108
6 2026-08-24 02:04 639231334732159368
37 ms 104.248.205.108
5 2026-08-24 01:48 639231325035670078
2214 ms 104.248.205.108
4 2026-08-24 01:32 639231315132253837
3 ms 104.248.205.108
3 2026-08-24 01:15 639231305014280808
3 ms 104.248.205.108
2 2026-08-24 00:23 639231273779380675
33 ms 104.248.205.108
1 2026-08-24 00:07 639231264180839154
156 ms 104.248.205.108