DNS response history for ns2.municipalidadlamas.gob.pe

ns2.municipalidadlamas.gob.pe 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 28 DNS check records, 27 successful responses, 1 failed responses, and 280 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.municipalidadlamas.gob.pe.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

280 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

62.171.190.123

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.municipalidadlamas.gob.pe

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
28 2026-08-26 09:09 639233318749762337
18 ms 62.171.190.123
27 2026-08-26 08:51 639233308387917838
2041 ms 62.171.190.123
26 2026-08-26 08:34 639233297961740122
2273 ms 62.171.190.123
25 2026-08-26 08:17 639233287487159094
101 ms 62.171.190.123
24 2026-08-26 07:59 639233276995531707
79 ms 62.171.190.123
23 2026-08-26 07:42 639233266521568229
-
22 2026-08-26 07:24 639233256081047431
68 ms 62.171.190.123
21 2026-08-26 06:30 639233223620132921
8 ms 62.171.190.123
20 2026-08-26 06:13 639233213287814244
19 ms 62.171.190.123
19 2026-08-26 05:56 639233202925983161
50 ms 62.171.190.123
18 2026-08-26 05:38 639233192644780696
52 ms 62.171.190.123
17 2026-08-26 05:21 639233182401183833
19 ms 62.171.190.123
16 2026-08-26 05:04 639233172074181051
78 ms 62.171.190.123
15 2026-08-26 04:47 639233161808421455
72 ms 62.171.190.123
14 2026-08-26 04:30 639233151357344052
2038 ms 62.171.190.123
13 2026-08-26 04:12 639233141034116946
77 ms 62.171.190.123
12 2026-08-26 03:55 639233130828334142
76 ms 62.171.190.123
11 2026-08-26 03:38 639233120373450007
37 ms 62.171.190.123
10 2026-08-26 03:21 639233110066216193
80 ms 62.171.190.123
9 2026-08-26 02:27 639233078065410564
37 ms 62.171.190.123
8 2026-08-26 02:10 639233067787457832
37 ms 62.171.190.123
7 2026-08-26 01:53 639233057501801162
57 ms 62.171.190.123
6 2026-08-26 01:36 639233047089431703
38 ms 62.171.190.123
5 2026-08-26 01:19 639233036754790688
23 ms 62.171.190.123
4 2026-08-26 01:01 639233026412602472
53 ms 62.171.190.123
3 2026-08-26 00:44 639233016064066127
62 ms 62.171.190.123
2 2026-08-26 00:27 639233005922655772
34 ms 62.171.190.123
1 2026-08-26 00:10 639232995672256907
24 ms 62.171.190.123