DNS response history for ns2.petachile.cl

ns2.petachile.cl 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 33 DNS check records, 33 successful responses, 0 failed responses, and 286 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.petachile.cl.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

286 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

181.212.43.58

Most recently resolved hosting IP on selected date

Successful Responses

33

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.petachile.cl

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
33 2026-08-25 11:33 639232535349285207
478 ms 181.212.43.58
32 2026-08-25 11:15 639232524938080723
461 ms 181.212.43.58
31 2026-08-25 10:22 639232492740373468
462 ms 181.212.43.58
30 2026-08-25 10:04 639232482235303141
3 ms 181.212.43.58
29 2026-08-25 09:47 639232471861770303
468 ms 181.212.43.58
28 2026-08-25 09:30 639232461630217327
457 ms 181.212.43.58
27 2026-08-25 09:13 639232451282965990
3 ms 181.212.43.58
26 2026-08-25 08:55 639232440814614938
466 ms 181.212.43.58
25 2026-08-25 08:38 639232430410720425
466 ms 181.212.43.58
24 2026-08-25 08:20 639232420003096185
462 ms 181.212.43.58
23 2026-08-25 08:03 639232409467287444
3 ms 181.212.43.58
22 2026-08-25 07:46 639232399077195997
467 ms 181.212.43.58
21 2026-08-25 07:28 639232388731528337
3 ms 181.212.43.58
20 2026-08-25 07:11 639232378288598612
470 ms 181.212.43.58
19 2026-08-25 06:17 639232346196373643
466 ms 181.212.43.58
18 2026-08-25 06:00 639232336112370741
464 ms 181.212.43.58
17 2026-08-25 05:44 639232326146508970
2 ms 181.212.43.58
16 2026-08-25 05:27 639232316189381720
3 ms 181.212.43.58
15 2026-08-25 05:11 639232306217998913
314 ms 181.212.43.58
14 2026-08-25 04:54 639232296255744174
4 ms 181.212.43.58
13 2026-08-25 04:37 639232286095760789
16 ms 181.212.43.58
12 2026-08-25 04:20 639232276086186273
465 ms 181.212.43.58
11 2026-08-25 04:03 639232265900986425
3 ms 181.212.43.58
10 2026-08-25 03:47 639232255723518075
465 ms 181.212.43.58
9 2026-08-25 03:29 639232245484452890
464 ms 181.212.43.58
8 2026-08-25 03:12 639232235157175331
235 ms 181.212.43.58
7 2026-08-25 02:19 639232203197189095
2 ms 181.212.43.58
6 2026-08-25 02:02 639232192844564298
464 ms 181.212.43.58
5 2026-08-25 01:45 639232182496008942
4 ms 181.212.43.58
4 2026-08-25 01:27 639232172197053132
469 ms 181.212.43.58
3 2026-08-25 00:34 639232140250307418
3 ms 181.212.43.58
2 2026-08-25 00:17 639232129927860324
458 ms 181.212.43.58
1 2026-08-25 00:00 639232119551972438
454 ms 181.212.43.58