DNS response history for ns1.hironickorea.co.kr

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

31

Historical checks stored for this nameserver on selected date

Average Latency

625 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.122.157.177

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 ns1.hironickorea.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
31 2026-08-27 10:09 639234212558002823
592 ms 116.122.157.177
30 2026-08-27 09:51 639234202117531850
591 ms 116.122.157.177
29 2026-08-27 09:34 639234191649612722
609 ms 116.122.157.177
28 2026-08-27 09:16 639234181105879568
904 ms 116.122.157.177
27 2026-08-27 08:59 639234170713214496
839 ms 116.122.157.177
26 2026-08-27 08:42 639234160341037652
847 ms 116.122.157.177
25 2026-08-27 08:24 639234149799404224
661 ms 116.122.157.177
24 2026-08-27 08:07 639234139553286469
612 ms 116.122.157.177
23 2026-08-27 07:13 639234107183588293
611 ms 116.122.157.177
22 2026-08-27 06:56 639234096905435724
600 ms 116.122.157.177
21 2026-08-27 06:39 639234086579410775
845 ms 116.122.157.177
20 2026-08-27 06:21 639234076291157956
623 ms 116.122.157.177
19 2026-08-27 06:04 639234065981939454
610 ms 116.122.157.177
18 2026-08-27 05:47 639234055548642997
595 ms 116.122.157.177
17 2026-08-27 05:30 639234045267979603
579 ms 116.122.157.177
16 2026-08-27 05:13 639234034999717463
600 ms 116.122.157.177
15 2026-08-27 04:55 639234024739225358
597 ms 116.122.157.177
14 2026-08-27 04:38 639234014311170162
614 ms 116.122.157.177
13 2026-08-27 04:21 639234003806017640
615 ms 116.122.157.177
12 2026-08-27 04:03 639233993356203030
613 ms 116.122.157.177
11 2026-08-27 03:10 639233961301716608
596 ms 116.122.157.177
10 2026-08-27 02:53 639233950834200647
761 ms 116.122.157.177
9 2026-08-27 02:35 639233940431849026
605 ms 116.122.157.177
8 2026-08-27 02:18 639233930110596398
279 ms 116.122.157.177
7 2026-08-27 02:01 639233919705434540
613 ms 116.122.157.177
6 2026-08-27 01:43 639233909452807845
589 ms 116.122.157.177
5 2026-08-27 01:26 639233899096420820
608 ms 116.122.157.177
4 2026-08-27 01:09 639233888707824939
617 ms 116.122.157.177
3 2026-08-27 00:52 639233878461203802
349 ms 116.122.157.177
2 2026-08-27 00:34 639233868060868209
600 ms 116.122.157.177
1 2026-08-27 00:17 639233857450922991
602 ms 116.122.157.177