DNS response history for ns2.chinaking.co.kr

ns2.chinaking.co.kr 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 32 DNS check records, 32 successful responses, 0 failed responses, and 571 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.chinaking.co.kr.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

571 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

218.145.65.144

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.chinaking.co.kr

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
32 2026-08-26 10:10 639233350067824371
562 ms 218.145.65.144
31 2026-08-26 09:53 639233339545274518
589 ms 218.145.65.144
30 2026-08-26 09:36 639233329214918079
578 ms 218.145.65.144
29 2026-08-26 09:18 639233318749762337
563 ms 218.145.65.144
28 2026-08-26 09:01 639233308387917838
622 ms 218.145.65.144
27 2026-08-26 08:44 639233297961740122
589 ms 218.145.65.144
26 2026-08-26 08:26 639233287487159094
567 ms 218.145.65.144
25 2026-08-26 08:09 639233276995531707
572 ms 218.145.65.144
24 2026-08-26 07:51 639233266521568229
550 ms 218.145.65.144
23 2026-08-26 07:34 639233256081047431
570 ms 218.145.65.144
22 2026-08-26 06:40 639233223620132921
565 ms 218.145.65.144
21 2026-08-26 06:22 639233213287814244
597 ms 218.145.65.144
20 2026-08-26 06:05 639233202925983161
555 ms 218.145.65.144
19 2026-08-26 05:48 639233192644780696
557 ms 218.145.65.144
18 2026-08-26 05:31 639233182401183833
566 ms 218.145.65.144
17 2026-08-26 05:14 639233172074181051
578 ms 218.145.65.144
16 2026-08-26 04:56 639233161808421455
585 ms 218.145.65.144
15 2026-08-26 04:39 639233151357344052
550 ms 218.145.65.144
14 2026-08-26 04:22 639233141034116946
571 ms 218.145.65.144
13 2026-08-26 04:05 639233130828334142
579 ms 218.145.65.144
12 2026-08-26 03:48 639233120373450007
562 ms 218.145.65.144
11 2026-08-26 03:30 639233110066216193
566 ms 218.145.65.144
10 2026-08-26 02:37 639233078065410564
556 ms 218.145.65.144
9 2026-08-26 02:20 639233067787457832
571 ms 218.145.65.144
8 2026-08-26 02:03 639233057501801162
564 ms 218.145.65.144
7 2026-08-26 01:46 639233047089431703
564 ms 218.145.65.144
6 2026-08-26 01:28 639233036754790688
573 ms 218.145.65.144
5 2026-08-26 01:11 639233026412602472
568 ms 218.145.65.144
4 2026-08-26 00:54 639233016064066127
574 ms 218.145.65.144
3 2026-08-26 00:37 639233005922655772
569 ms 218.145.65.144
2 2026-08-26 00:20 639232995672256907
584 ms 218.145.65.144
1 2026-08-26 00:02 639232985300872416
553 ms 218.145.65.144