DNS response history for ns2.alitech.biz

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

36

Historical checks stored for this nameserver on selected date

Average Latency

501 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

158.160.1.100

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.alitech.biz

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
36 2026-08-26 12:09 639233424567558554
2020 ms 158.160.1.100
35 2026-08-26 11:52 639233414056832719
51 ms 158.160.1.100
34 2026-08-26 11:34 639233403515141099
58 ms 158.160.1.100
33 2026-08-26 10:40 639233370841350248
45 ms 158.160.1.100
32 2026-08-26 10:22 639233360361507238
61 ms 158.160.1.100
31 2026-08-26 10:05 639233350067824371
72 ms 158.160.1.100
30 2026-08-26 09:48 639233339545274518
39 ms 158.160.1.100
29 2026-08-26 09:30 639233329214918079
50 ms 158.160.1.100
28 2026-08-26 09:13 639233318749762337
19 ms 158.160.1.100
27 2026-08-26 08:56 639233308387917838
44 ms 158.160.1.100
26 2026-08-26 08:38 639233297961740122
41 ms 158.160.1.100
25 2026-08-26 08:21 639233287487159094
44 ms 158.160.1.100
24 2026-08-26 08:04 639233276995531707
50 ms 158.160.1.100
23 2026-08-26 07:46 639233266521568229
76 ms 158.160.1.100
22 2026-08-26 07:29 639233256081047431
50 ms 158.160.1.100
21 2026-08-26 06:35 639233223620132921
51 ms 158.160.1.100
20 2026-08-26 06:17 639233213287814244
58 ms 158.160.1.100
19 2026-08-26 06:00 639233202925983161
1524 ms 158.160.1.100
18 2026-08-26 05:43 639233192644780696
47 ms 158.160.1.100
17 2026-08-26 05:26 639233182401183833
46 ms 158.160.1.100
16 2026-08-26 05:09 639233172074181051
1532 ms 158.160.1.100
15 2026-08-26 04:51 639233161808421455
2014 ms 158.160.1.100
14 2026-08-26 04:34 639233151357344052
42 ms 158.160.1.100
13 2026-08-26 04:17 639233141034116946
2022 ms 158.160.1.100
12 2026-08-26 04:00 639233130828334142
47 ms 158.160.1.100
11 2026-08-26 03:43 639233120373450007
48 ms 158.160.1.100
10 2026-08-26 03:25 639233110066216193
3522 ms 158.160.1.100
9 2026-08-26 02:32 639233078065410564
57 ms 158.160.1.100
8 2026-08-26 02:15 639233067787457832
49 ms 158.160.1.100
7 2026-08-26 01:58 639233057501801162
52 ms 158.160.1.100
6 2026-08-26 01:40 639233047089431703
30 ms 158.160.1.100
5 2026-08-26 01:23 639233036754790688
43 ms 158.160.1.100
4 2026-08-26 01:06 639233026412602472
45 ms 158.160.1.100
3 2026-08-26 00:49 639233016064066127
51 ms 158.160.1.100
2 2026-08-26 00:32 639233005922655772
4030 ms 158.160.1.100
1 2026-08-26 00:15 639232995672256907
17 ms 158.160.1.100