DNS response history for ns2.controlhelm14.com

ns2.controlhelm14.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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 327 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.controlhelm14.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

327 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.180.33.229

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.controlhelm14.com

Showing DNS history for 2026-08-26 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-26 11:35 639233403515141099
265 ms 66.180.33.229
33 2026-08-26 10:40 639233370841350248
266 ms 66.180.33.229
32 2026-08-26 10:23 639233360361507238
267 ms 66.180.33.229
31 2026-08-26 10:06 639233350067824371
279 ms 66.180.33.229
30 2026-08-26 09:49 639233339545274518
265 ms 66.180.33.229
29 2026-08-26 09:31 639233329214918079
279 ms 66.180.33.229
28 2026-08-26 09:14 639233318749762337
2153 ms 66.180.33.229
27 2026-08-26 08:56 639233308387917838
167 ms 66.180.33.229
26 2026-08-26 08:39 639233297961740122
257 ms 66.180.33.229
25 2026-08-26 08:22 639233287487159094
278 ms 66.180.33.229
24 2026-08-26 08:04 639233276995531707
273 ms 66.180.33.229
23 2026-08-26 07:46 639233266521568229
266 ms 66.180.33.229
22 2026-08-26 07:29 639233256081047431
238 ms 66.180.33.229
21 2026-08-26 06:35 639233223620132921
266 ms 66.180.33.229
20 2026-08-26 06:18 639233213287814244
3 ms 66.180.33.229
19 2026-08-26 06:01 639233202925983161
290 ms 66.180.33.229
18 2026-08-26 05:43 639233192644780696
2034 ms 66.180.33.229
17 2026-08-26 05:26 639233182401183833
137 ms 66.180.33.229
16 2026-08-26 05:09 639233172074181051
275 ms 66.180.33.229
15 2026-08-26 04:52 639233161808421455
137 ms 66.180.33.229
14 2026-08-26 04:35 639233151357344052
4 ms 66.180.33.229
13 2026-08-26 04:17 639233141034116946
268 ms 66.180.33.229
12 2026-08-26 04:00 639233130828334142
268 ms 66.180.33.229
11 2026-08-26 03:43 639233120373450007
268 ms 66.180.33.229
10 2026-08-26 03:26 639233110066216193
132 ms 66.180.33.229
9 2026-08-26 02:32 639233078065410564
266 ms 66.180.33.229
8 2026-08-26 02:15 639233067787457832
272 ms 66.180.33.229
7 2026-08-26 01:58 639233057501801162
145 ms 66.180.33.229
6 2026-08-26 01:41 639233047089431703
276 ms 66.180.33.229
5 2026-08-26 01:24 639233036754790688
8 ms 66.180.33.229
4 2026-08-26 01:06 639233026412602472
142 ms 66.180.33.229
3 2026-08-26 00:49 639233016064066127
133 ms 66.180.33.229
2 2026-08-26 00:32 639233005922655772
262 ms 66.180.33.229
1 2026-08-26 00:15 639232995672256907
266 ms 66.180.33.229