DNS response history for ns2.lanlos.info

ns2.lanlos.info 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 34 DNS check records, 34 successful responses, 0 failed responses, and 466 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.lanlos.info.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

466 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.23.160.180

Most recently resolved hosting IP on selected date

Successful Responses

34

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.lanlos.info

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
34 2026-08-26 11:31 639233403515141099
2031 ms 94.23.160.180
33 2026-08-26 10:36 639233370841350248
35 ms 94.23.160.180
32 2026-08-26 10:19 639233360361507238
153 ms 94.23.160.180
31 2026-08-26 10:02 639233350067824371
396 ms 94.23.160.180
30 2026-08-26 09:44 639233339545274518
52 ms 94.23.160.180
29 2026-08-26 09:27 639233329214918079
145 ms 94.23.160.180
28 2026-08-26 09:09 639233318749762337
410 ms 94.23.160.180
27 2026-08-26 08:52 639233308387917838
43 ms 94.23.160.180
26 2026-08-26 08:35 639233297961740122
4017 ms 94.23.160.180
25 2026-08-26 08:17 639233287487159094
124 ms 94.23.160.180
24 2026-08-26 08:00 639233276995531707
2034 ms 94.23.160.180
23 2026-08-26 07:42 639233266521568229
66 ms 94.23.160.180
22 2026-08-26 07:25 639233256081047431
515 ms 94.23.160.180
21 2026-08-26 06:31 639233223620132921
40 ms 94.23.160.180
20 2026-08-26 06:14 639233213287814244
541 ms 94.23.160.180
19 2026-08-26 05:56 639233202925983161
27 ms 94.23.160.180
18 2026-08-26 05:39 639233192644780696
517 ms 94.23.160.180
17 2026-08-26 05:22 639233182401183833
199 ms 94.23.160.180
16 2026-08-26 05:05 639233172074181051
50 ms 94.23.160.180
15 2026-08-26 04:48 639233161808421455
49 ms 94.23.160.180
14 2026-08-26 04:30 639233151357344052
396 ms 94.23.160.180
13 2026-08-26 04:13 639233141034116946
54 ms 94.23.160.180
12 2026-08-26 03:56 639233130828334142
32 ms 94.23.160.180
11 2026-08-26 03:39 639233120373450007
27 ms 94.23.160.180
10 2026-08-26 03:21 639233110066216193
810 ms 94.23.160.180
9 2026-08-26 02:28 639233078065410564
29 ms 94.23.160.180
8 2026-08-26 02:11 639233067787457832
44 ms 94.23.160.180
7 2026-08-26 01:54 639233057501801162
39 ms 94.23.160.180
6 2026-08-26 01:37 639233047089431703
20 ms 94.23.160.180
5 2026-08-26 01:19 639233036754790688
22 ms 94.23.160.180
4 2026-08-26 01:02 639233026412602472
182 ms 94.23.160.180
3 2026-08-26 00:45 639233016064066127
167 ms 94.23.160.180
2 2026-08-26 00:28 639233005922655772
2075 ms 94.23.160.180
1 2026-08-26 00:11 639232995672256907
505 ms 94.23.160.180