DNS response history for ns2.helauto.com

ns2.helauto.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 36 DNS check records, 36 successful responses, 0 failed responses, and 326 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.helauto.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

326 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

158.255.46.168

Most recently resolved hosting IP on selected date

Successful Responses

36

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.helauto.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
36 2026-08-24 15:14 639231807961539652
29 ms 158.255.46.168
35 2026-08-24 14:57 639231797631669865
46 ms 158.255.46.168
34 2026-08-24 14:04 639231765923559455
64 ms 158.255.46.168
33 2026-08-24 13:47 639231755868832964
28 ms 158.255.46.168
32 2026-08-24 13:30 639231745628278877
24 ms 158.255.46.168
31 2026-08-24 13:13 639231735407682062
59 ms 158.255.46.168
30 2026-08-24 12:20 639231703815441688
153 ms 158.255.46.168
29 2026-08-24 12:04 639231693747052549
80 ms 158.255.46.168
28 2026-08-24 11:47 639231683712487276
63 ms 158.255.46.168
27 2026-08-24 11:30 639231673513573868
34 ms 158.255.46.168
26 2026-08-24 10:37 639231641791249939
29 ms 158.255.46.168
25 2026-08-24 10:20 639231631866211033
97 ms 158.255.46.168
24 2026-08-24 10:03 639231621644955316
2056 ms 158.255.46.168
23 2026-08-24 09:46 639231611478799259
59 ms 158.255.46.168
22 2026-08-24 08:54 639231579923718211
2067 ms 158.255.46.168
21 2026-08-24 08:37 639231569810702936
39 ms 158.255.46.168
20 2026-08-24 08:20 639231559762411619
6 ms 158.255.46.168
19 2026-08-24 08:03 639231549663595407
5 ms 158.255.46.168
18 2026-08-24 07:11 639231518076817246
14 ms 158.255.46.168
17 2026-08-24 06:54 639231508078650885
61 ms 158.255.46.168
16 2026-08-24 06:38 639231498210697093
64 ms 158.255.46.168
15 2026-08-24 06:21 639231488109699360
47 ms 158.255.46.168
14 2026-08-24 05:29 639231456772510692
60 ms 158.255.46.168
13 2026-08-24 05:13 639231447084631185
59 ms 158.255.46.168
12 2026-08-24 04:56 639231437208519473
2 ms 158.255.46.168
11 2026-08-24 04:39 639231427209627490
58 ms 158.255.46.168
10 2026-08-24 03:47 639231395791246644
63 ms 158.255.46.168
9 2026-08-24 03:31 639231386075551458
7 ms 158.255.46.168
8 2026-08-24 03:14 639231376208713791
4075 ms 158.255.46.168
7 2026-08-24 02:58 639231366170589276
13 ms 158.255.46.168
6 2026-08-24 02:05 639231334732159368
52 ms 158.255.46.168
5 2026-08-24 01:49 639231325035670078
2 ms 158.255.46.168
4 2026-08-24 01:32 639231315132253837
2087 ms 158.255.46.168
3 2026-08-24 01:16 639231305014280808
69 ms 158.255.46.168
2 2026-08-24 00:24 639231273779380675
59 ms 158.255.46.168
1 2026-08-24 00:08 639231264180839154
8 ms 158.255.46.168