DNS response history for ns2.halsys.com

ns2.halsys.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 31 DNS check records, 30 successful responses, 1 failed responses, and 237 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.halsys.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

237 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

97.107.128.250

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns2.halsys.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
31 2026-08-26 10:07 639233350067824371
202 ms 97.107.128.250
30 2026-08-26 09:49 639233339545274518
209 ms 97.107.128.250
29 2026-08-26 09:32 639233329214918079
106 ms 97.107.128.250
28 2026-08-26 09:15 639233318749762337
206 ms 97.107.128.250
27 2026-08-26 08:57 639233308387917838
201 ms 97.107.128.250
26 2026-08-26 08:40 639233297961740122
192 ms 97.107.128.250
25 2026-08-26 08:22 639233287487159094
121 ms 97.107.128.250
24 2026-08-26 08:05 639233276995531707
162 ms 97.107.128.250
23 2026-08-26 07:47 639233266521568229
209 ms 97.107.128.250
22 2026-08-26 07:30 639233256081047431
207 ms 97.107.128.250
21 2026-08-26 06:36 639233223620132921
206 ms 97.107.128.250
20 2026-08-26 06:19 639233213287814244
107 ms 97.107.128.250
19 2026-08-26 06:01 639233202925983161
209 ms 97.107.128.250
18 2026-08-26 05:44 639233192644780696
210 ms 97.107.128.250
17 2026-08-26 05:27 639233182401183833
203 ms 97.107.128.250
16 2026-08-26 05:10 639233172074181051
202 ms 97.107.128.250
15 2026-08-26 04:53 639233161808421455
217 ms 97.107.128.250
14 2026-08-26 04:36 639233151357344052
104 ms 97.107.128.250
13 2026-08-26 04:18 639233141034116946
98 ms 97.107.128.250
12 2026-08-26 04:01 639233130828334142
202 ms 97.107.128.250
11 2026-08-26 03:44 639233120373450007
-
10 2026-08-26 03:27 639233110066216193
205 ms 97.107.128.250
9 2026-08-26 02:33 639233078065410564
100 ms 97.107.128.250
8 2026-08-26 02:16 639233067787457832
100 ms 97.107.128.250
7 2026-08-26 01:59 639233057501801162
205 ms 97.107.128.250
6 2026-08-26 01:42 639233047089431703
98 ms 97.107.128.250
5 2026-08-26 01:25 639233036754790688
210 ms 97.107.128.250
4 2026-08-26 01:07 639233026412602472
206 ms 97.107.128.250
3 2026-08-26 00:50 639233016064066127
201 ms 97.107.128.250
2 2026-08-26 00:33 639233005922655772
2100 ms 97.107.128.250
1 2026-08-26 00:16 639232995672256907
105 ms 97.107.128.250