DNS response history for ns2.deepcube.co.kr

ns2.deepcube.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-24. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 719 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.deepcube.co.kr.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

719 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:27

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

30

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

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
30 2026-08-24 12:27 639231703815441688
588 ms 218.145.65.144
29 2026-08-24 12:10 639231693747052549
650 ms 218.145.65.144
28 2026-08-24 11:53 639231683712487276
603 ms 218.145.65.144
27 2026-08-24 11:36 639231673513573868
617 ms 218.145.65.144
26 2026-08-24 10:43 639231641791249939
1131 ms 218.145.65.144
25 2026-08-24 10:27 639231631866211033
556 ms 218.145.65.144
24 2026-08-24 10:10 639231621644955316
561 ms 218.145.65.144
23 2026-08-24 09:53 639231611478799259
566 ms 218.145.65.144
22 2026-08-24 09:00 639231579923718211
793 ms 218.145.65.144
21 2026-08-24 08:44 639231569810702936
790 ms 218.145.65.144
20 2026-08-24 08:27 639231559762411619
621 ms 218.145.65.144
19 2026-08-24 08:10 639231549663595407
729 ms 218.145.65.144
18 2026-08-24 07:17 639231518076817246
497 ms 218.145.65.144
17 2026-08-24 07:01 639231508078650885
2 ms 218.145.65.144
16 2026-08-24 06:44 639231498210697093
677 ms 218.145.65.144
15 2026-08-24 06:27 639231488109699360
1186 ms 218.145.65.144
14 2026-08-24 05:35 639231456772510692
887 ms 218.145.65.144
13 2026-08-24 05:19 639231447084631185
894 ms 218.145.65.144
12 2026-08-24 05:02 639231437208519473
3 ms 218.145.65.144
11 2026-08-24 04:46 639231427209627490
895 ms 218.145.65.144
10 2026-08-24 03:53 639231395791246644
297 ms 218.145.65.144
9 2026-08-24 03:37 639231386075551458
1014 ms 218.145.65.144
8 2026-08-24 03:21 639231376208713791
1157 ms 218.145.65.144
7 2026-08-24 03:04 639231366170589276
841 ms 218.145.65.144
6 2026-08-24 02:12 639231334732159368
1172 ms 218.145.65.144
5 2026-08-24 01:55 639231325035670078
2 ms 218.145.65.144
4 2026-08-24 01:39 639231315132253837
856 ms 218.145.65.144
3 2026-08-24 01:22 639231305014280808
1217 ms 218.145.65.144
2 2026-08-24 00:30 639231273779380675
1192 ms 218.145.65.144
1 2026-08-24 00:14 639231264180839154
590 ms 218.145.65.144