DNS response history for ns2.controlhelm5.com

ns2.controlhelm5.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 409 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.controlhelm5.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

409 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.180.33.205

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.controlhelm5.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:20 639232566381512620
273 ms 66.180.33.205
34 2026-08-25 12:03 639232556111768563
2191 ms 66.180.33.205
33 2026-08-25 11:46 639232545839529039
276 ms 66.180.33.205
32 2026-08-25 11:29 639232535349285207
276 ms 66.180.33.205
31 2026-08-25 11:11 639232524938080723
268 ms 66.180.33.205
30 2026-08-25 10:17 639232492740373468
267 ms 66.180.33.205
29 2026-08-25 10:00 639232482235303141
2263 ms 66.180.33.205
28 2026-08-25 09:43 639232471861770303
175 ms 66.180.33.205
27 2026-08-25 09:25 639232461630217327
268 ms 66.180.33.205
26 2026-08-25 09:08 639232451282965990
262 ms 66.180.33.205
25 2026-08-25 08:51 639232440814614938
263 ms 66.180.33.205
24 2026-08-25 08:33 639232430410720425
274 ms 66.180.33.205
23 2026-08-25 08:16 639232420003096185
273 ms 66.180.33.205
22 2026-08-25 07:59 639232409467287444
23 ms 66.180.33.205
21 2026-08-25 07:41 639232399077195997
269 ms 66.180.33.205
20 2026-08-25 07:24 639232388731528337
277 ms 66.180.33.205
19 2026-08-25 07:07 639232378288598612
272 ms 66.180.33.205
18 2026-08-25 06:13 639232346196373643
3 ms 66.180.33.205
17 2026-08-25 05:56 639232336112370741
265 ms 66.180.33.205
16 2026-08-25 05:40 639232326146508970
277 ms 66.180.33.205
15 2026-08-25 05:23 639232316189381720
2139 ms 66.180.33.205
14 2026-08-25 05:06 639232306217998913
133 ms 66.180.33.205
13 2026-08-25 04:50 639232296255744174
281 ms 66.180.33.205
12 2026-08-25 04:33 639232286095760789
138 ms 66.180.33.205
11 2026-08-25 04:16 639232276086186273
264 ms 66.180.33.205
10 2026-08-25 03:59 639232265900986425
280 ms 66.180.33.205
9 2026-08-25 03:42 639232255723518075
272 ms 66.180.33.205
8 2026-08-25 03:25 639232245484452890
284 ms 66.180.33.205
7 2026-08-25 03:08 639232235157175331
279 ms 66.180.33.205
6 2026-08-25 02:15 639232203197189095
266 ms 66.180.33.205
5 2026-08-25 01:58 639232192844564298
280 ms 66.180.33.205
4 2026-08-25 01:40 639232182496008942
260 ms 66.180.33.205
3 2026-08-25 01:23 639232172197053132
140 ms 66.180.33.205
2 2026-08-25 00:30 639232140250307418
286 ms 66.180.33.205
1 2026-08-25 00:13 639232129927860324
281 ms 66.180.33.205