DNS response history for ns2.active4web.com

ns2.active4web.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 39 DNS check records, 38 successful responses, 1 failed responses, and 193 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.active4web.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

193 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 16:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

65.108.7.199

Most recently resolved hosting IP on selected date

Successful Responses

38

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 ns2.active4web.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
39 2026-08-24 16:38 639231860258429562
69 ms 65.108.7.199
38 2026-08-24 15:44 639231828211839931
164 ms 65.108.7.199
37 2026-08-24 15:27 639231818080917481
129 ms 65.108.7.199
36 2026-08-24 15:10 639231807961539652
73 ms 65.108.7.199
35 2026-08-24 14:53 639231797631669865
144 ms 65.108.7.199
34 2026-08-24 14:00 639231765923559455
-
33 2026-08-24 13:43 639231755868832964
40 ms 65.108.7.199
32 2026-08-24 13:26 639231745628278877
149 ms 65.108.7.199
31 2026-08-24 13:09 639231735407682062
67 ms 65.108.7.199
30 2026-08-24 12:17 639231703815441688
121 ms 65.108.7.199
29 2026-08-24 12:00 639231693747052549
121 ms 65.108.7.199
28 2026-08-24 11:43 639231683712487276
62 ms 65.108.7.199
27 2026-08-24 11:26 639231673513573868
134 ms 65.108.7.199
26 2026-08-24 10:33 639231641791249939
130 ms 65.108.7.199
25 2026-08-24 10:17 639231631866211033
9 ms 65.108.7.199
24 2026-08-24 10:00 639231621644955316
35 ms 65.108.7.199
23 2026-08-24 09:43 639231611478799259
2063 ms 65.108.7.199
22 2026-08-24 08:50 639231579923718211
138 ms 65.108.7.199
21 2026-08-24 08:33 639231569810702936
6 ms 65.108.7.199
20 2026-08-24 08:17 639231559762411619
98 ms 65.108.7.199
19 2026-08-24 08:00 639231549663595407
126 ms 65.108.7.199
18 2026-08-24 07:07 639231518076817246
169 ms 65.108.7.199
17 2026-08-24 06:51 639231508078650885
49 ms 65.108.7.199
16 2026-08-24 06:34 639231498210697093
2151 ms 65.108.7.199
15 2026-08-24 06:17 639231488109699360
149 ms 65.108.7.199
14 2026-08-24 05:25 639231456772510692
14 ms 65.108.7.199
13 2026-08-24 05:09 639231447084631185
22 ms 65.108.7.199
12 2026-08-24 04:52 639231437208519473
8 ms 65.108.7.199
11 2026-08-24 04:36 639231427209627490
126 ms 65.108.7.199
10 2026-08-24 03:43 639231395791246644
59 ms 65.108.7.199
9 2026-08-24 03:27 639231386075551458
153 ms 65.108.7.199
8 2026-08-24 03:11 639231376208713791
121 ms 65.108.7.199
7 2026-08-24 02:54 639231366170589276
7 ms 65.108.7.199
6 2026-08-24 02:02 639231334732159368
5 ms 65.108.7.199
5 2026-08-24 01:45 639231325035670078
49 ms 65.108.7.199
4 2026-08-24 01:29 639231315132253837
9 ms 65.108.7.199
3 2026-08-24 01:12 639231305014280808
101 ms 65.108.7.199
2 2026-08-24 00:20 639231273779380675
126 ms 65.108.7.199
1 2026-08-24 00:04 639231264180839154
127 ms 65.108.7.199