DNS response history for ns2.clnetworks.com

ns2.clnetworks.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, 34 successful responses, 0 failed responses, and 397 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.clnetworks.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

397 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.114.148.250

Most recently resolved hosting IP on selected date

Successful Responses

34

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.clnetworks.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:07 639231765923559455
92 ms 74.114.148.250
33 2026-08-24 13:50 639231755868832964
203 ms 74.114.148.250
32 2026-08-24 13:33 639231745628278877
187 ms 74.114.148.250
31 2026-08-24 13:16 639231735407682062
4 ms 74.114.148.250
30 2026-08-24 12:23 639231703815441688
1599 ms 74.114.148.250
29 2026-08-24 12:06 639231693747052549
2 ms 74.114.148.250
28 2026-08-24 11:49 639231683712487276
2 ms 74.114.148.250
27 2026-08-24 11:33 639231673513573868
1753 ms 74.114.148.250
26 2026-08-24 10:39 639231641791249939
99 ms 74.114.148.250
25 2026-08-24 10:23 639231631866211033
188 ms 74.114.148.250
24 2026-08-24 10:06 639231621644955316
102 ms 74.114.148.250
23 2026-08-24 09:49 639231611478799259
4 ms 74.114.148.250
22 2026-08-24 08:57 639231579923718211
5 ms 74.114.148.250
21 2026-08-24 08:40 639231569810702936
4 ms 74.114.148.250
20 2026-08-24 08:23 639231559762411619
189 ms 74.114.148.250
19 2026-08-24 08:06 639231549663595407
184 ms 74.114.148.250
18 2026-08-24 07:13 639231518076817246
102 ms 74.114.148.250
17 2026-08-24 06:57 639231508078650885
183 ms 74.114.148.250
16 2026-08-24 06:40 639231498210697093
190 ms 74.114.148.250
15 2026-08-24 06:24 639231488109699360
188 ms 74.114.148.250
14 2026-08-24 05:31 639231456772510692
183 ms 74.114.148.250
13 2026-08-24 05:15 639231447084631185
1597 ms 74.114.148.250
12 2026-08-24 04:59 639231437208519473
105 ms 74.114.148.250
11 2026-08-24 04:42 639231427209627490
4117 ms 74.114.148.250
10 2026-08-24 03:49 639231395791246644
1680 ms 74.114.148.250
9 2026-08-24 03:33 639231386075551458
3 ms 74.114.148.250
8 2026-08-24 03:17 639231376208713791
5 ms 74.114.148.250
7 2026-08-24 03:00 639231366170589276
8 ms 74.114.148.250
6 2026-08-24 02:08 639231334732159368
121 ms 74.114.148.250
5 2026-08-24 01:52 639231325035670078
23 ms 74.114.148.250
4 2026-08-24 01:35 639231315132253837
181 ms 74.114.148.250
3 2026-08-24 01:18 639231305014280808
3 ms 74.114.148.250
2 2026-08-24 00:26 639231273779380675
193 ms 74.114.148.250
1 2026-08-24 00:10 639231264180839154
2 ms 74.114.148.250