DNS response history for ns2.hostname.co.kr

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

27

Historical checks stored for this nameserver on selected date

Average Latency

695 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.110.18.232

Most recently resolved hosting IP on selected date

Successful Responses

27

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

Showing DNS history for 2026-08-27 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
27 2026-08-27 08:59 639234170713214496
623 ms 211.110.18.232
26 2026-08-27 08:41 639234160341037652
602 ms 211.110.18.232
25 2026-08-27 08:24 639234149799404224
1004 ms 211.110.18.232
24 2026-08-27 08:06 639234139553286469
631 ms 211.110.18.232
23 2026-08-27 07:13 639234107183588293
616 ms 211.110.18.232
22 2026-08-27 06:56 639234096905435724
605 ms 211.110.18.232
21 2026-08-27 06:38 639234086579410775
594 ms 211.110.18.232
20 2026-08-27 06:21 639234076291157956
626 ms 211.110.18.232
19 2026-08-27 06:04 639234065981939454
620 ms 211.110.18.232
18 2026-08-27 05:47 639234055548642997
2347 ms 211.110.18.232
17 2026-08-27 05:29 639234045267979603
607 ms 211.110.18.232
16 2026-08-27 05:12 639234034999717463
617 ms 211.110.18.232
15 2026-08-27 04:55 639234024739225358
609 ms 211.110.18.232
14 2026-08-27 04:38 639234014311170162
602 ms 211.110.18.232
13 2026-08-27 04:21 639234003806017640
628 ms 211.110.18.232
12 2026-08-27 04:03 639233993356203030
621 ms 211.110.18.232
11 2026-08-27 03:10 639233961301716608
615 ms 211.110.18.232
10 2026-08-27 02:52 639233950834200647
643 ms 211.110.18.232
9 2026-08-27 02:35 639233940431849026
624 ms 211.110.18.232
8 2026-08-27 02:18 639233930110596398
621 ms 211.110.18.232
7 2026-08-27 02:00 639233919705434540
607 ms 211.110.18.232
6 2026-08-27 01:43 639233909452807845
633 ms 211.110.18.232
5 2026-08-27 01:26 639233899096420820
622 ms 211.110.18.232
4 2026-08-27 01:09 639233888707824939
611 ms 211.110.18.232
3 2026-08-27 00:51 639233878461203802
618 ms 211.110.18.232
2 2026-08-27 00:34 639233868060868209
615 ms 211.110.18.232
1 2026-08-27 00:17 639233857450922991
612 ms 211.110.18.232