DNS response history for ns2.starpik.com

ns2.starpik.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-24. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 265 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.starpik.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

265 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

176.123.6.120

Most recently resolved hosting IP on selected date

Successful Responses

29

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.starpik.com

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
29 2026-08-24 12:01 639231693747052549
81 ms 176.123.6.120
28 2026-08-24 11:44 639231683712487276
2071 ms 176.123.6.120
27 2026-08-24 11:27 639231673513573868
97 ms 176.123.6.120
26 2026-08-24 10:34 639231641791249939
59 ms 176.123.6.120
25 2026-08-24 10:18 639231631866211033
7 ms 176.123.6.120
24 2026-08-24 10:01 639231621644955316
86 ms 176.123.6.120
23 2026-08-24 09:44 639231611478799259
2032 ms 176.123.6.120
22 2026-08-24 08:51 639231579923718211
90 ms 176.123.6.120
21 2026-08-24 08:34 639231569810702936
91 ms 176.123.6.120
20 2026-08-24 08:17 639231559762411619
77 ms 176.123.6.120
19 2026-08-24 08:01 639231549663595407
26 ms 176.123.6.120
18 2026-08-24 07:08 639231518076817246
91 ms 176.123.6.120
17 2026-08-24 06:52 639231508078650885
80 ms 176.123.6.120
16 2026-08-24 06:35 639231498210697093
10 ms 176.123.6.120
15 2026-08-24 06:18 639231488109699360
39 ms 176.123.6.120
14 2026-08-24 05:26 639231456772510692
13 ms 176.123.6.120
13 2026-08-24 05:10 639231447084631185
115 ms 176.123.6.120
12 2026-08-24 04:53 639231437208519473
93 ms 176.123.6.120
11 2026-08-24 04:37 639231427209627490
80 ms 176.123.6.120
10 2026-08-24 03:44 639231395791246644
73 ms 176.123.6.120
9 2026-08-24 03:28 639231386075551458
10 ms 176.123.6.120
8 2026-08-24 03:12 639231376208713791
3 ms 176.123.6.120
7 2026-08-24 02:55 639231366170589276
77 ms 176.123.6.120
6 2026-08-24 02:03 639231334732159368
58 ms 176.123.6.120
5 2026-08-24 01:46 639231325035670078
79 ms 176.123.6.120
4 2026-08-24 01:30 639231315132253837
2008 ms 176.123.6.120
3 2026-08-24 01:13 639231305014280808
65 ms 176.123.6.120
2 2026-08-24 00:21 639231273779380675
69 ms 176.123.6.120
1 2026-08-24 00:05 639231264180839154
13 ms 176.123.6.120