DNS response history for ns1.helastel.com

ns1.helastel.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 37 DNS check records, 36 successful responses, 1 failed responses, and 253 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 ns1.helastel.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

253 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

87.237.69.104

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns1.helastel.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
37 2026-08-26 12:21 639233434974187439
114 ms 87.237.69.104
36 2026-08-26 12:04 639233424567558554
102 ms 87.237.69.104
35 2026-08-26 11:46 639233414056832719
66 ms 87.237.69.104
34 2026-08-26 11:29 639233403515141099
158 ms 87.237.69.104
33 2026-08-26 10:34 639233370841350248
100 ms 87.237.69.104
32 2026-08-26 10:17 639233360361507238
98 ms 87.237.69.104
31 2026-08-26 10:00 639233350067824371
98 ms 87.237.69.104
30 2026-08-26 09:42 639233339545274518
85 ms 87.237.69.104
29 2026-08-26 09:25 639233329214918079
33 ms 87.237.69.104
28 2026-08-26 09:08 639233318749762337
89 ms 87.237.69.104
27 2026-08-26 08:50 639233308387917838
68 ms 87.237.69.104
26 2026-08-26 08:33 639233297961740122
73 ms 87.237.69.104
25 2026-08-26 08:15 639233287487159094
76 ms 87.237.69.104
24 2026-08-26 07:58 639233276995531707
10 ms 87.237.69.104
23 2026-08-26 07:40 639233266521568229
100 ms 87.237.69.104
22 2026-08-26 07:23 639233256081047431
13 ms 87.237.69.104
21 2026-08-26 06:29 639233223620132921
-
20 2026-08-26 06:12 639233213287814244
98 ms 87.237.69.104
19 2026-08-26 05:55 639233202925983161
70 ms 87.237.69.104
18 2026-08-26 05:37 639233192644780696
70 ms 87.237.69.104
17 2026-08-26 05:20 639233182401183833
101 ms 87.237.69.104
16 2026-08-26 05:03 639233172074181051
43 ms 87.237.69.104
15 2026-08-26 04:46 639233161808421455
79 ms 87.237.69.104
14 2026-08-26 04:29 639233151357344052
61 ms 87.237.69.104
13 2026-08-26 04:11 639233141034116946
71 ms 87.237.69.104
12 2026-08-26 03:54 639233130828334142
127 ms 87.237.69.104
11 2026-08-26 03:37 639233120373450007
101 ms 87.237.69.104
10 2026-08-26 03:20 639233110066216193
80 ms 87.237.69.104
9 2026-08-26 02:26 639233078065410564
2077 ms 87.237.69.104
8 2026-08-26 02:09 639233067787457832
103 ms 87.237.69.104
7 2026-08-26 01:52 639233057501801162
2024 ms 87.237.69.104
6 2026-08-26 01:35 639233047089431703
52 ms 87.237.69.104
5 2026-08-26 01:18 639233036754790688
168 ms 87.237.69.104
4 2026-08-26 01:00 639233026412602472
145 ms 87.237.69.104
3 2026-08-26 00:43 639233016064066127
192 ms 87.237.69.104
2 2026-08-26 00:26 639233005922655772
2094 ms 87.237.69.104
1 2026-08-26 00:09 639232995672256907
86 ms 87.237.69.104