DNS response history for ns1.lanlos.info

ns1.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-25. For this date, NameServerHistory found 30 DNS check records, 29 successful responses, 1 failed responses, and 575 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 ns1.lanlos.info.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

575 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:13

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

29

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

Showing DNS history for 2026-08-25 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
30 2026-08-25 10:13 639232492740373468
2064 ms 94.23.160.180
29 2026-08-25 09:55 639232482235303141
69 ms 94.23.160.180
28 2026-08-25 09:38 639232471861770303
2023 ms 94.23.160.180
27 2026-08-25 09:21 639232461630217327
98 ms 94.23.160.180
26 2026-08-25 09:04 639232451282965990
2298 ms 94.23.160.180
25 2026-08-25 08:46 639232440814614938
437 ms 94.23.160.180
24 2026-08-25 08:29 639232430410720425
50 ms 94.23.160.180
23 2026-08-25 08:12 639232420003096185
2143 ms 94.23.160.180
22 2026-08-25 07:54 639232409467287444
23 ms 94.23.160.180
21 2026-08-25 07:37 639232399077195997
149 ms 94.23.160.180
20 2026-08-25 07:19 639232388731528337
45 ms 94.23.160.180
19 2026-08-25 07:02 639232378288598612
2039 ms 94.23.160.180
18 2026-08-25 06:09 639232346196373643
276 ms 94.23.160.180
17 2026-08-25 05:52 639232336112370741
33 ms 94.23.160.180
16 2026-08-25 05:35 639232326146508970
71 ms 94.23.160.180
15 2026-08-25 05:19 639232316189381720
-
14 2026-08-25 05:02 639232306217998913
50 ms 94.23.160.180
13 2026-08-25 04:45 639232296255744174
2021 ms 94.23.160.180
12 2026-08-25 04:28 639232286095760789
13 ms 94.23.160.180
11 2026-08-25 04:12 639232276086186273
37 ms 94.23.160.180
10 2026-08-25 03:55 639232265900986425
23 ms 94.23.160.180
9 2026-08-25 03:38 639232255723518075
2027 ms 94.23.160.180
8 2026-08-25 03:21 639232245484452890
46 ms 94.23.160.180
7 2026-08-25 03:04 639232235157175331
53 ms 94.23.160.180
6 2026-08-25 02:10 639232203197189095
46 ms 94.23.160.180
5 2026-08-25 01:53 639232192844564298
227 ms 94.23.160.180
4 2026-08-25 01:36 639232182496008942
60 ms 94.23.160.180
3 2026-08-25 01:19 639232172197053132
170 ms 94.23.160.180
2 2026-08-25 00:25 639232140250307418
11 ms 94.23.160.180
1 2026-08-25 00:08 639232129927860324
59 ms 94.23.160.180