DNS response history for ns2.hoimyung.co.kr

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

31

Historical checks stored for this nameserver on selected date

Average Latency

653 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.169.74.3

Most recently resolved hosting IP on selected date

Successful Responses

31

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.hoimyung.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
31 2026-08-26 09:53 639233339545274518
628 ms 211.169.74.3
30 2026-08-26 09:36 639233329214918079
605 ms 211.169.74.3
29 2026-08-26 09:19 639233318749762337
619 ms 211.169.74.3
28 2026-08-26 09:01 639233308387917838
733 ms 211.169.74.3
27 2026-08-26 08:44 639233297961740122
605 ms 211.169.74.3
26 2026-08-26 08:26 639233287487159094
713 ms 211.169.74.3
25 2026-08-26 08:09 639233276995531707
635 ms 211.169.74.3
24 2026-08-26 07:51 639233266521568229
598 ms 211.169.74.3
23 2026-08-26 07:34 639233256081047431
625 ms 211.169.74.3
22 2026-08-26 06:40 639233223620132921
602 ms 211.169.74.3
21 2026-08-26 06:23 639233213287814244
611 ms 211.169.74.3
20 2026-08-26 06:05 639233202925983161
653 ms 211.169.74.3
19 2026-08-26 05:48 639233192644780696
634 ms 211.169.74.3
18 2026-08-26 05:31 639233182401183833
593 ms 211.169.74.3
17 2026-08-26 05:14 639233172074181051
627 ms 211.169.74.3
16 2026-08-26 04:57 639233161808421455
3 ms 211.169.74.3
15 2026-08-26 04:40 639233151357344052
3 ms 211.169.74.3
14 2026-08-26 04:22 639233141034116946
637 ms 211.169.74.3
13 2026-08-26 04:05 639233130828334142
600 ms 211.169.74.3
12 2026-08-26 03:48 639233120373450007
618 ms 211.169.74.3
11 2026-08-26 03:30 639233110066216193
624 ms 211.169.74.3
10 2026-08-26 02:37 639233078065410564
625 ms 211.169.74.3
9 2026-08-26 02:20 639233067787457832
880 ms 211.169.74.3
8 2026-08-26 02:03 639233057501801162
2273 ms 211.169.74.3
7 2026-08-26 01:46 639233047089431703
604 ms 211.169.74.3
6 2026-08-26 01:28 639233036754790688
831 ms 211.169.74.3
5 2026-08-26 01:11 639233026412602472
625 ms 211.169.74.3
4 2026-08-26 00:54 639233016064066127
638 ms 211.169.74.3
3 2026-08-26 00:37 639233005922655772
588 ms 211.169.74.3
2 2026-08-26 00:20 639232995672256907
596 ms 211.169.74.3
1 2026-08-26 00:03 639232985300872416
620 ms 211.169.74.3