DNS response history for ns3.chileadmin.com

ns3.chileadmin.com 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 35 DNS check records, 35 successful responses, 0 failed responses, and 525 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 ns3.chileadmin.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

525 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.59.166.150

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns3.chileadmin.com

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
35 2026-08-26 11:38 639233403515141099
357 ms 209.59.166.150
34 2026-08-26 10:43 639233370841350248
495 ms 209.59.166.150
33 2026-08-26 10:26 639233360361507238
494 ms 209.59.166.150
32 2026-08-26 10:08 639233350067824371
500 ms 209.59.166.150
31 2026-08-26 09:51 639233339545274518
642 ms 209.59.166.150
30 2026-08-26 09:34 639233329214918079
495 ms 209.59.166.150
29 2026-08-26 09:16 639233318749762337
267 ms 209.59.166.150
28 2026-08-26 08:59 639233308387917838
491 ms 209.59.166.150
27 2026-08-26 08:42 639233297961740122
613 ms 209.59.166.150
26 2026-08-26 08:24 639233287487159094
491 ms 209.59.166.150
25 2026-08-26 08:07 639233276995531707
301 ms 209.59.166.150
24 2026-08-26 07:49 639233266521568229
587 ms 209.59.166.150
23 2026-08-26 07:32 639233256081047431
509 ms 209.59.166.150
22 2026-08-26 06:38 639233223620132921
490 ms 209.59.166.150
21 2026-08-26 06:21 639233213287814244
492 ms 209.59.166.150
20 2026-08-26 06:03 639233202925983161
489 ms 209.59.166.150
19 2026-08-26 05:46 639233192644780696
293 ms 209.59.166.150
18 2026-08-26 05:29 639233182401183833
489 ms 209.59.166.150
17 2026-08-26 05:12 639233172074181051
490 ms 209.59.166.150
16 2026-08-26 04:55 639233161808421455
498 ms 209.59.166.150
15 2026-08-26 04:38 639233151357344052
492 ms 209.59.166.150
14 2026-08-26 04:20 639233141034116946
2229 ms 209.59.166.150
13 2026-08-26 04:03 639233130828334142
489 ms 209.59.166.150
12 2026-08-26 03:46 639233120373450007
490 ms 209.59.166.150
11 2026-08-26 03:28 639233110066216193
489 ms 209.59.166.150
10 2026-08-26 02:35 639233078065410564
494 ms 209.59.166.150
9 2026-08-26 02:18 639233067787457832
482 ms 209.59.166.150
8 2026-08-26 02:01 639233057501801162
488 ms 209.59.166.150
7 2026-08-26 01:44 639233047089431703
505 ms 209.59.166.150
6 2026-08-26 01:26 639233036754790688
488 ms 209.59.166.150
5 2026-08-26 01:09 639233026412602472
490 ms 209.59.166.150
4 2026-08-26 00:52 639233016064066127
519 ms 209.59.166.150
3 2026-08-26 00:35 639233005922655772
490 ms 209.59.166.150
2 2026-08-26 00:18 639232995672256907
241 ms 209.59.166.150
1 2026-08-26 00:01 639232985300872416
503 ms 209.59.166.150