DNS response history for ns2.starkeykorea.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

662 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

220.73.160.47

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.starkeykorea.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
34 2026-08-24 14:11 639231765923559455
869 ms 220.73.160.47
33 2026-08-24 13:54 639231755868832964
580 ms 220.73.160.47
32 2026-08-24 13:37 639231745628278877
576 ms 220.73.160.47
31 2026-08-24 13:20 639231735407682062
871 ms 220.73.160.47
30 2026-08-24 12:27 639231703815441688
600 ms 220.73.160.47
29 2026-08-24 12:11 639231693747052549
585 ms 220.73.160.47
28 2026-08-24 11:54 639231683712487276
593 ms 220.73.160.47
27 2026-08-24 11:37 639231673513573868
569 ms 220.73.160.47
26 2026-08-24 10:44 639231641791249939
877 ms 220.73.160.47
25 2026-08-24 10:27 639231631866211033
585 ms 220.73.160.47
24 2026-08-24 10:11 639231621644955316
878 ms 220.73.160.47
23 2026-08-24 09:53 639231611478799259
588 ms 220.73.160.47
22 2026-08-24 09:01 639231579923718211
899 ms 220.73.160.47
21 2026-08-24 08:44 639231569810702936
891 ms 220.73.160.47
20 2026-08-24 08:27 639231559762411619
569 ms 220.73.160.47
19 2026-08-24 08:10 639231549663595407
597 ms 220.73.160.47
18 2026-08-24 07:17 639231518076817246
3 ms 220.73.160.47
17 2026-08-24 07:01 639231508078650885
890 ms 220.73.160.47
16 2026-08-24 06:44 639231498210697093
276 ms 220.73.160.47
15 2026-08-24 06:28 639231488109699360
573 ms 220.73.160.47
14 2026-08-24 05:35 639231456772510692
865 ms 220.73.160.47
13 2026-08-24 05:19 639231447084631185
585 ms 220.73.160.47
12 2026-08-24 05:03 639231437208519473
879 ms 220.73.160.47
11 2026-08-24 04:46 639231427209627490
581 ms 220.73.160.47
10 2026-08-24 03:53 639231395791246644
864 ms 220.73.160.47
9 2026-08-24 03:37 639231386075551458
3 ms 220.73.160.47
8 2026-08-24 03:21 639231376208713791
883 ms 220.73.160.47
7 2026-08-24 03:05 639231366170589276
592 ms 220.73.160.47
6 2026-08-24 02:12 639231334732159368
573 ms 220.73.160.47
5 2026-08-24 01:56 639231325035670078
880 ms 220.73.160.47
4 2026-08-24 01:39 639231315132253837
878 ms 220.73.160.47
3 2026-08-24 01:23 639231305014280808
887 ms 220.73.160.47
2 2026-08-24 00:30 639231273779380675
557 ms 220.73.160.47
1 2026-08-24 00:14 639231264180839154
609 ms 220.73.160.47