DNS response history for ns1.leadfly.com

ns1.leadfly.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 38 DNS check records, 38 successful responses, 0 failed responses, and 340 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.leadfly.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

340 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.116.116.102

Most recently resolved hosting IP on selected date

Successful Responses

38

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 ns1.leadfly.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
38 2026-08-24 15:50 639231828211839931
4008 ms 50.116.116.102
37 2026-08-24 15:33 639231818080917481
248 ms 50.116.116.102
36 2026-08-24 15:15 639231807961539652
235 ms 50.116.116.102
35 2026-08-24 14:59 639231797631669865
117 ms 50.116.116.102
34 2026-08-24 14:06 639231765923559455
235 ms 50.116.116.102
33 2026-08-24 13:49 639231755868832964
126 ms 50.116.116.102
32 2026-08-24 13:32 639231745628278877
11 ms 50.116.116.102
31 2026-08-24 13:15 639231735407682062
239 ms 50.116.116.102
30 2026-08-24 12:22 639231703815441688
238 ms 50.116.116.102
29 2026-08-24 12:05 639231693747052549
236 ms 50.116.116.102
28 2026-08-24 11:48 639231683712487276
2141 ms 50.116.116.102
27 2026-08-24 11:32 639231673513573868
4 ms 50.116.116.102
26 2026-08-24 10:39 639231641791249939
5 ms 50.116.116.102
25 2026-08-24 10:22 639231631866211033
4 ms 50.116.116.102
24 2026-08-24 10:05 639231621644955316
239 ms 50.116.116.102
23 2026-08-24 09:48 639231611478799259
244 ms 50.116.116.102
22 2026-08-24 08:56 639231579923718211
4 ms 50.116.116.102
21 2026-08-24 08:39 639231569810702936
183 ms 50.116.116.102
20 2026-08-24 08:22 639231559762411619
4 ms 50.116.116.102
19 2026-08-24 08:05 639231549663595407
236 ms 50.116.116.102
18 2026-08-24 07:13 639231518076817246
240 ms 50.116.116.102
17 2026-08-24 06:56 639231508078650885
238 ms 50.116.116.102
16 2026-08-24 06:39 639231498210697093
163 ms 50.116.116.102
15 2026-08-24 06:23 639231488109699360
9 ms 50.116.116.102
14 2026-08-24 05:30 639231456772510692
236 ms 50.116.116.102
13 2026-08-24 05:14 639231447084631185
8 ms 50.116.116.102
12 2026-08-24 04:58 639231437208519473
118 ms 50.116.116.102
11 2026-08-24 04:41 639231427209627490
4 ms 50.116.116.102
10 2026-08-24 03:49 639231395791246644
2009 ms 50.116.116.102
9 2026-08-24 03:33 639231386075551458
130 ms 50.116.116.102
8 2026-08-24 03:16 639231376208713791
251 ms 50.116.116.102
7 2026-08-24 02:59 639231366170589276
131 ms 50.116.116.102
6 2026-08-24 02:07 639231334732159368
269 ms 50.116.116.102
5 2026-08-24 01:51 639231325035670078
116 ms 50.116.116.102
4 2026-08-24 01:34 639231315132253837
12 ms 50.116.116.102
3 2026-08-24 01:18 639231305014280808
234 ms 50.116.116.102
2 2026-08-24 00:25 639231273779380675
7 ms 50.116.116.102
1 2026-08-24 00:09 639231264180839154
4 ms 50.116.116.102