DNS response history for ns1.landm.net

ns1.landm.net 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 31 DNS check records, 31 successful responses, 0 failed responses, and 44 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.landm.net.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

44 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.12.159.130

Most recently resolved hosting IP on selected date

Successful Responses

31

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 ns1.landm.net

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
31 2026-08-25 11:05 639232524938080723
23 ms 49.12.159.130
30 2026-08-25 10:11 639232492740373468
46 ms 49.12.159.130
29 2026-08-25 09:54 639232482235303141
29 ms 49.12.159.130
28 2026-08-25 09:37 639232471861770303
41 ms 49.12.159.130
27 2026-08-25 09:20 639232461630217327
53 ms 49.12.159.130
26 2026-08-25 09:02 639232451282965990
39 ms 49.12.159.130
25 2026-08-25 08:45 639232440814614938
47 ms 49.12.159.130
24 2026-08-25 08:27 639232430410720425
53 ms 49.12.159.130
23 2026-08-25 08:10 639232420003096185
57 ms 49.12.159.130
22 2026-08-25 07:53 639232409467287444
48 ms 49.12.159.130
21 2026-08-25 07:35 639232399077195997
38 ms 49.12.159.130
20 2026-08-25 07:18 639232388731528337
71 ms 49.12.159.130
19 2026-08-25 07:01 639232378288598612
50 ms 49.12.159.130
18 2026-08-25 06:07 639232346196373643
25 ms 49.12.159.130
17 2026-08-25 05:50 639232336112370741
30 ms 49.12.159.130
16 2026-08-25 05:34 639232326146508970
37 ms 49.12.159.130
15 2026-08-25 05:17 639232316189381720
63 ms 49.12.159.130
14 2026-08-25 05:00 639232306217998913
6 ms 49.12.159.130
13 2026-08-25 04:44 639232296255744174
39 ms 49.12.159.130
12 2026-08-25 04:27 639232286095760789
34 ms 49.12.159.130
11 2026-08-25 04:10 639232276086186273
36 ms 49.12.159.130
10 2026-08-25 03:53 639232265900986425
45 ms 49.12.159.130
9 2026-08-25 03:36 639232255723518075
61 ms 49.12.159.130
8 2026-08-25 03:19 639232245484452890
37 ms 49.12.159.130
7 2026-08-25 03:02 639232235157175331
66 ms 49.12.159.130
6 2026-08-25 02:09 639232203197189095
65 ms 49.12.159.130
5 2026-08-25 01:52 639232192844564298
72 ms 49.12.159.130
4 2026-08-25 01:34 639232182496008942
13 ms 49.12.159.130
3 2026-08-25 01:17 639232172197053132
63 ms 49.12.159.130
2 2026-08-25 00:24 639232140250307418
28 ms 49.12.159.130
1 2026-08-25 00:07 639232129927860324
38 ms 49.12.159.130