DNS response history for ns2.aloserv.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

1485 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

165.140.70.56

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

7

Checks with no response or no returned latency

Failure Rate

19%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.aloserv.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
36 2026-08-26 11:59 639233414056832719
234 ms 165.140.70.56
35 2026-08-26 11:42 639233403515141099
118 ms 165.140.70.56
34 2026-08-26 10:47 639233370841350248
117 ms 165.140.70.56
33 2026-08-26 10:30 639233360361507238
118 ms 165.140.70.56
32 2026-08-26 10:12 639233350067824371
236 ms 165.140.70.56
31 2026-08-26 09:55 639233339545274518
241 ms 165.140.70.56
30 2026-08-26 09:38 639233329214918079
247 ms 165.140.70.56
29 2026-08-26 09:21 639233318749762337
232 ms 165.140.70.56
28 2026-08-26 09:03 639233308387917838
234 ms 165.140.70.56
27 2026-08-26 08:46 639233297961740122
236 ms 165.140.70.56
26 2026-08-26 08:28 639233287487159094
118 ms 165.140.70.56
25 2026-08-26 08:11 639233276995531707
231 ms 165.140.70.56
24 2026-08-26 07:53 639233266521568229
117 ms 165.140.70.56
23 2026-08-26 07:36 639233256081047431
233 ms 165.140.70.56
22 2026-08-26 06:42 639233223620132921
234 ms 165.140.70.56
21 2026-08-26 06:25 639233213287814244
235 ms 165.140.70.56
20 2026-08-26 06:07 639233202925983161
-
19 2026-08-26 05:50 639233192644780696
2008 ms 165.140.70.56
18 2026-08-26 05:33 639233182401183833
3137 ms 165.140.70.56
17 2026-08-26 05:16 639233172074181051
-
16 2026-08-26 04:59 639233161808421455
4009 ms 165.140.70.56
15 2026-08-26 04:41 639233151357344052
2008 ms 165.140.70.56
14 2026-08-26 04:24 639233141034116946
-
13 2026-08-26 04:07 639233130828334142
2146 ms 165.140.70.56
12 2026-08-26 03:50 639233120373450007
4010 ms 165.140.70.56
11 2026-08-26 03:32 639233110066216193
4148 ms 165.140.70.56
10 2026-08-26 02:39 639233078065410564
-
9 2026-08-26 02:22 639233067787457832
2010 ms 165.140.70.56
8 2026-08-26 02:05 639233057501801162
-
7 2026-08-26 01:48 639233047089431703
2032 ms 165.140.70.56
6 2026-08-26 01:30 639233036754790688
-
5 2026-08-26 01:13 639233026412602472
4008 ms 165.140.70.56
4 2026-08-26 00:56 639233016064066127
4131 ms 165.140.70.56
3 2026-08-26 00:39 639233005922655772
2238 ms 165.140.70.56
2 2026-08-26 00:22 639232995672256907
4009 ms 165.140.70.56
1 2026-08-26 00:05 639232985300872416
-