DNS response history for ns2.starkmedia.cl

ns2.starkmedia.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-24. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 287 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.starkmedia.cl.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

287 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.5.119

Most recently resolved hosting IP on selected date

Successful Responses

32

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

Showing DNS history for 2026-08-24 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
32 2026-08-24 13:23 639231745628278877
15 ms 162.240.5.119
31 2026-08-24 13:06 639231735407682062
55 ms 162.240.5.119
30 2026-08-24 12:13 639231703815441688
32 ms 162.240.5.119
29 2026-08-24 11:56 639231693747052549
95 ms 162.240.5.119
28 2026-08-24 11:39 639231683712487276
43 ms 162.240.5.119
27 2026-08-24 11:22 639231673513573868
2038 ms 162.240.5.119
26 2026-08-24 10:29 639231641791249939
2051 ms 162.240.5.119
25 2026-08-24 10:13 639231631866211033
25 ms 162.240.5.119
24 2026-08-24 09:56 639231621644955316
2071 ms 162.240.5.119
23 2026-08-24 09:39 639231611478799259
22 ms 162.240.5.119
22 2026-08-24 08:46 639231579923718211
14 ms 162.240.5.119
21 2026-08-24 08:30 639231569810702936
16 ms 162.240.5.119
20 2026-08-24 08:13 639231559762411619
10 ms 162.240.5.119
19 2026-08-24 07:56 639231549663595407
2246 ms 162.240.5.119
18 2026-08-24 07:03 639231518076817246
60 ms 162.240.5.119
17 2026-08-24 06:47 639231508078650885
36 ms 162.240.5.119
16 2026-08-24 06:30 639231498210697093
26 ms 162.240.5.119
15 2026-08-24 06:13 639231488109699360
11 ms 162.240.5.119
14 2026-08-24 05:21 639231456772510692
37 ms 162.240.5.119
13 2026-08-24 05:05 639231447084631185
18 ms 162.240.5.119
12 2026-08-24 04:49 639231437208519473
7 ms 162.240.5.119
11 2026-08-24 04:32 639231427209627490
17 ms 162.240.5.119
10 2026-08-24 03:39 639231395791246644
10 ms 162.240.5.119
9 2026-08-24 03:23 639231386075551458
18 ms 162.240.5.119
8 2026-08-24 03:07 639231376208713791
13 ms 162.240.5.119
7 2026-08-24 02:50 639231366170589276
9 ms 162.240.5.119
6 2026-08-24 01:58 639231334732159368
38 ms 162.240.5.119
5 2026-08-24 01:42 639231325035670078
64 ms 162.240.5.119
4 2026-08-24 01:25 639231315132253837
16 ms 162.240.5.119
3 2026-08-24 01:08 639231305014280808
21 ms 162.240.5.119
2 2026-08-24 00:16 639231273779380675
12 ms 162.240.5.119
1 2026-08-24 00:00 639231264180839154
49 ms 162.240.5.119