DNS response history for ns2.cbnuh.or.kr

ns2.cbnuh.or.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 34 DNS check records, 34 successful responses, 0 failed responses, and 416 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.cbnuh.or.kr.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

416 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

220.83.87.2

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.cbnuh.or.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
34 2026-08-24 14:10 639231765923559455
4 ms 220.83.87.2
33 2026-08-24 13:53 639231755868832964
585 ms 220.83.87.2
32 2026-08-24 13:36 639231745628278877
610 ms 220.83.87.2
31 2026-08-24 13:19 639231735407682062
612 ms 220.83.87.2
30 2026-08-24 12:26 639231703815441688
584 ms 220.83.87.2
29 2026-08-24 12:10 639231693747052549
4 ms 220.83.87.2
28 2026-08-24 11:53 639231683712487276
572 ms 220.83.87.2
27 2026-08-24 11:36 639231673513573868
596 ms 220.83.87.2
26 2026-08-24 10:43 639231641791249939
569 ms 220.83.87.2
25 2026-08-24 10:26 639231631866211033
576 ms 220.83.87.2
24 2026-08-24 10:10 639231621644955316
589 ms 220.83.87.2
23 2026-08-24 09:53 639231611478799259
594 ms 220.83.87.2
22 2026-08-24 09:00 639231579923718211
586 ms 220.83.87.2
21 2026-08-24 08:43 639231569810702936
4 ms 220.83.87.2
20 2026-08-24 08:26 639231559762411619
4 ms 220.83.87.2
19 2026-08-24 08:09 639231549663595407
575 ms 220.83.87.2
18 2026-08-24 07:17 639231518076817246
3 ms 220.83.87.2
17 2026-08-24 07:00 639231508078650885
568 ms 220.83.87.2
16 2026-08-24 06:44 639231498210697093
3 ms 220.83.87.2
15 2026-08-24 06:27 639231488109699360
576 ms 220.83.87.2
14 2026-08-24 05:35 639231456772510692
291 ms 220.83.87.2
13 2026-08-24 05:18 639231447084631185
589 ms 220.83.87.2
12 2026-08-24 05:02 639231437208519473
3 ms 220.83.87.2
11 2026-08-24 04:45 639231427209627490
616 ms 220.83.87.2
10 2026-08-24 03:53 639231395791246644
33 ms 220.83.87.2
9 2026-08-24 03:37 639231386075551458
2 ms 220.83.87.2
8 2026-08-24 03:20 639231376208713791
282 ms 220.83.87.2
7 2026-08-24 03:04 639231366170589276
590 ms 220.83.87.2
6 2026-08-24 02:11 639231334732159368
599 ms 220.83.87.2
5 2026-08-24 01:55 639231325035670078
586 ms 220.83.87.2
4 2026-08-24 01:39 639231315132253837
590 ms 220.83.87.2
3 2026-08-24 01:22 639231305014280808
571 ms 220.83.87.2
2 2026-08-24 00:29 639231273779380675
570 ms 220.83.87.2
1 2026-08-24 00:13 639231264180839154
598 ms 220.83.87.2