DNS response history for ns2.controlhelm29.com

ns2.controlhelm29.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-25. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 352 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.controlhelm29.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

352 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:19

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

35

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

Showing DNS history for 2026-08-25 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
35 2026-08-25 12:19 639232566381512620
272 ms 66.180.33.229
34 2026-08-25 12:02 639232556111768563
7 ms 66.180.33.229
33 2026-08-25 11:45 639232545839529039
269 ms 66.180.33.229
32 2026-08-25 11:28 639232535349285207
279 ms 66.180.33.229
31 2026-08-25 11:10 639232524938080723
142 ms 66.180.33.229
30 2026-08-25 10:17 639232492740373468
142 ms 66.180.33.229
29 2026-08-25 10:00 639232482235303141
2031 ms 66.180.33.229
28 2026-08-25 09:42 639232471861770303
32 ms 66.180.33.229
27 2026-08-25 09:25 639232461630217327
132 ms 66.180.33.229
26 2026-08-25 09:08 639232451282965990
131 ms 66.180.33.229
25 2026-08-25 08:50 639232440814614938
130 ms 66.180.33.229
24 2026-08-25 08:33 639232430410720425
271 ms 66.180.33.229
23 2026-08-25 08:16 639232420003096185
30 ms 66.180.33.229
22 2026-08-25 07:58 639232409467287444
278 ms 66.180.33.229
21 2026-08-25 07:41 639232399077195997
2134 ms 66.180.33.229
20 2026-08-25 07:23 639232388731528337
285 ms 66.180.33.229
19 2026-08-25 07:06 639232378288598612
134 ms 66.180.33.229
18 2026-08-25 06:12 639232346196373643
270 ms 66.180.33.229
17 2026-08-25 05:55 639232336112370741
147 ms 66.180.33.229
16 2026-08-25 05:39 639232326146508970
269 ms 66.180.33.229
15 2026-08-25 05:22 639232316189381720
19 ms 66.180.33.229
14 2026-08-25 05:06 639232306217998913
138 ms 66.180.33.229
13 2026-08-25 04:49 639232296255744174
282 ms 66.180.33.229
12 2026-08-25 04:32 639232286095760789
143 ms 66.180.33.229
11 2026-08-25 04:15 639232276086186273
138 ms 66.180.33.229
10 2026-08-25 03:59 639232265900986425
269 ms 66.180.33.229
9 2026-08-25 03:42 639232255723518075
140 ms 66.180.33.229
8 2026-08-25 03:24 639232245484452890
269 ms 66.180.33.229
7 2026-08-25 03:07 639232235157175331
264 ms 66.180.33.229
6 2026-08-25 02:14 639232203197189095
2188 ms 66.180.33.229
5 2026-08-25 01:57 639232192844564298
267 ms 66.180.33.229
4 2026-08-25 01:40 639232182496008942
274 ms 66.180.33.229
3 2026-08-25 01:22 639232172197053132
266 ms 66.180.33.229
2 2026-08-25 00:29 639232140250307418
9 ms 66.180.33.229
1 2026-08-25 00:12 639232129927860324
268 ms 66.180.33.229