DNS response history for ns2.conservaperu.org

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

34

Historical checks stored for this nameserver on selected date

Average Latency

317 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

154.38.183.8

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.conservaperu.org

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
34 2026-08-25 11:56 639232556111768563
291 ms 154.38.183.8
33 2026-08-25 11:39 639232545839529039
197 ms 154.38.183.8
32 2026-08-25 11:22 639232535349285207
182 ms 154.38.183.8
31 2026-08-25 11:05 639232524938080723
42 ms 154.38.183.8
30 2026-08-25 10:11 639232492740373468
54 ms 154.38.183.8
29 2026-08-25 09:53 639232482235303141
33 ms 154.38.183.8
28 2026-08-25 09:36 639232471861770303
247 ms 154.38.183.8
27 2026-08-25 09:19 639232461630217327
64 ms 154.38.183.8
26 2026-08-25 09:02 639232451282965990
281 ms 154.38.183.8
25 2026-08-25 08:44 639232440814614938
15 ms 154.38.183.8
24 2026-08-25 08:27 639232430410720425
58 ms 154.38.183.8
23 2026-08-25 08:10 639232420003096185
2221 ms 154.38.183.8
22 2026-08-25 07:52 639232409467287444
20 ms 154.38.183.8
21 2026-08-25 07:35 639232399077195997
21 ms 154.38.183.8
20 2026-08-25 07:18 639232388731528337
150 ms 154.38.183.8
19 2026-08-25 07:00 639232378288598612
2048 ms 154.38.183.8
18 2026-08-25 06:07 639232346196373643
2017 ms 154.38.183.8
17 2026-08-25 05:50 639232336112370741
4 ms 154.38.183.8
16 2026-08-25 05:33 639232326146508970
65 ms 154.38.183.8
15 2026-08-25 05:17 639232316189381720
19 ms 154.38.183.8
14 2026-08-25 05:00 639232306217998913
196 ms 154.38.183.8
13 2026-08-25 04:44 639232296255744174
28 ms 154.38.183.8
12 2026-08-25 04:27 639232286095760789
32 ms 154.38.183.8
11 2026-08-25 04:10 639232276086186273
25 ms 154.38.183.8
10 2026-08-25 03:53 639232265900986425
157 ms 154.38.183.8
9 2026-08-25 03:36 639232255723518075
84 ms 154.38.183.8
8 2026-08-25 03:19 639232245484452890
32 ms 154.38.183.8
7 2026-08-25 03:02 639232235157175331
65 ms 154.38.183.8
6 2026-08-25 02:08 639232203197189095
2029 ms 154.38.183.8
5 2026-08-25 01:51 639232192844564298
34 ms 154.38.183.8
4 2026-08-25 01:34 639232182496008942
9 ms 154.38.183.8
3 2026-08-25 01:17 639232172197053132
7 ms 154.38.183.8
2 2026-08-25 00:23 639232140250307418
22 ms 154.38.183.8
1 2026-08-25 00:06 639232129927860324
36 ms 154.38.183.8