DNS response history for ns2.hankyung.com

ns2.hankyung.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 466 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.hankyung.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

466 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.96.202.2

Most recently resolved hosting IP on selected date

Successful Responses

35

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.hankyung.com

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
35 2026-08-26 11:38 639233403515141099
596 ms 210.96.202.2
34 2026-08-26 10:44 639233370841350248
595 ms 210.96.202.2
33 2026-08-26 10:27 639233360361507238
603 ms 210.96.202.2
32 2026-08-26 10:09 639233350067824371
223 ms 210.96.202.2
31 2026-08-26 09:52 639233339545274518
574 ms 210.96.202.2
30 2026-08-26 09:34 639233329214918079
282 ms 210.96.202.2
29 2026-08-26 09:17 639233318749762337
298 ms 210.96.202.2
28 2026-08-26 09:00 639233308387917838
296 ms 210.96.202.2
27 2026-08-26 08:43 639233297961740122
281 ms 210.96.202.2
26 2026-08-26 08:25 639233287487159094
571 ms 210.96.202.2
25 2026-08-26 08:08 639233276995531707
288 ms 210.96.202.2
24 2026-08-26 07:50 639233266521568229
585 ms 210.96.202.2
23 2026-08-26 07:33 639233256081047431
302 ms 210.96.202.2
22 2026-08-26 06:39 639233223620132921
313 ms 210.96.202.2
21 2026-08-26 06:21 639233213287814244
319 ms 210.96.202.2
20 2026-08-26 06:04 639233202925983161
284 ms 210.96.202.2
19 2026-08-26 05:47 639233192644780696
301 ms 210.96.202.2
18 2026-08-26 05:30 639233182401183833
612 ms 210.96.202.2
17 2026-08-26 05:13 639233172074181051
571 ms 210.96.202.2
16 2026-08-26 04:55 639233161808421455
269 ms 210.96.202.2
15 2026-08-26 04:38 639233151357344052
298 ms 210.96.202.2
14 2026-08-26 04:21 639233141034116946
559 ms 210.96.202.2
13 2026-08-26 04:04 639233130828334142
582 ms 210.96.202.2
12 2026-08-26 03:47 639233120373450007
611 ms 210.96.202.2
11 2026-08-26 03:29 639233110066216193
567 ms 210.96.202.2
10 2026-08-26 02:36 639233078065410564
592 ms 210.96.202.2
9 2026-08-26 02:19 639233067787457832
585 ms 210.96.202.2
8 2026-08-26 02:02 639233057501801162
2269 ms 210.96.202.2
7 2026-08-26 01:44 639233047089431703
10 ms 210.96.202.2
6 2026-08-26 01:27 639233036754790688
3 ms 210.96.202.2
5 2026-08-26 01:10 639233026412602472
589 ms 210.96.202.2
4 2026-08-26 00:53 639233016064066127
577 ms 210.96.202.2
3 2026-08-26 00:36 639233005922655772
305 ms 210.96.202.2
2 2026-08-26 00:18 639232995672256907
295 ms 210.96.202.2
1 2026-08-26 00:01 639232985300872416
291 ms 210.96.202.2