DNS response history for ns2.aloask.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

667 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

173.249.60.135

Most recently resolved hosting IP on selected date

Successful Responses

29

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.aloask.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
29 2026-08-26 09:26 639233329214918079
2045 ms 173.249.60.135
28 2026-08-26 09:08 639233318749762337
4104 ms 173.249.60.135
27 2026-08-26 08:51 639233308387917838
42 ms 173.249.60.135
26 2026-08-26 08:33 639233297961740122
34 ms 173.249.60.135
25 2026-08-26 08:16 639233287487159094
2052 ms 173.249.60.135
24 2026-08-26 07:59 639233276995531707
73 ms 173.249.60.135
23 2026-08-26 07:41 639233266521568229
37 ms 173.249.60.135
22 2026-08-26 07:24 639233256081047431
51 ms 173.249.60.135
21 2026-08-26 06:30 639233223620132921
48 ms 173.249.60.135
20 2026-08-26 06:12 639233213287814244
25 ms 173.249.60.135
19 2026-08-26 05:55 639233202925983161
2043 ms 173.249.60.135
18 2026-08-26 05:38 639233192644780696
2059 ms 173.249.60.135
17 2026-08-26 05:21 639233182401183833
4 ms 173.249.60.135
16 2026-08-26 05:04 639233172074181051
18 ms 173.249.60.135
15 2026-08-26 04:47 639233161808421455
39 ms 173.249.60.135
14 2026-08-26 04:29 639233151357344052
37 ms 173.249.60.135
13 2026-08-26 04:12 639233141034116946
36 ms 173.249.60.135
12 2026-08-26 03:55 639233130828334142
80 ms 173.249.60.135
11 2026-08-26 03:38 639233120373450007
2089 ms 173.249.60.135
10 2026-08-26 03:20 639233110066216193
61 ms 173.249.60.135
9 2026-08-26 02:27 639233078065410564
52 ms 173.249.60.135
8 2026-08-26 02:10 639233067787457832
48 ms 173.249.60.135
7 2026-08-26 01:53 639233057501801162
17 ms 173.249.60.135
6 2026-08-26 01:35 639233047089431703
2070 ms 173.249.60.135
5 2026-08-26 01:18 639233036754790688
23 ms 173.249.60.135
4 2026-08-26 01:01 639233026412602472
2023 ms 173.249.60.135
3 2026-08-26 00:44 639233016064066127
70 ms 173.249.60.135
2 2026-08-26 00:27 639233005922655772
18 ms 173.249.60.135
1 2026-08-26 00:10 639232995672256907
40 ms 173.249.60.135