DNS response history for ns.kisline.co.kr

ns.kisline.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 34 DNS check records, 34 successful responses, 0 failed responses, and 572 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 ns.kisline.co.kr.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

572 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

121.162.154.3

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 ns.kisline.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
34 2026-08-27 11:00 639234243654907465
592 ms 121.162.154.3
33 2026-08-27 10:43 639234233269654413
593 ms 121.162.154.3
32 2026-08-27 10:26 639234222943951923
601 ms 121.162.154.3
31 2026-08-27 10:09 639234212558002823
588 ms 121.162.154.3
30 2026-08-27 09:51 639234202117531850
584 ms 121.162.154.3
29 2026-08-27 09:34 639234191649612722
601 ms 121.162.154.3
28 2026-08-27 09:16 639234181105879568
597 ms 121.162.154.3
27 2026-08-27 08:59 639234170713214496
608 ms 121.162.154.3
26 2026-08-27 08:42 639234160341037652
595 ms 121.162.154.3
25 2026-08-27 08:24 639234149799404224
583 ms 121.162.154.3
24 2026-08-27 08:07 639234139553286469
608 ms 121.162.154.3
23 2026-08-27 07:13 639234107183588293
611 ms 121.162.154.3
22 2026-08-27 06:56 639234096905435724
598 ms 121.162.154.3
21 2026-08-27 06:38 639234086579410775
562 ms 121.162.154.3
20 2026-08-27 06:21 639234076291157956
595 ms 121.162.154.3
19 2026-08-27 06:04 639234065981939454
584 ms 121.162.154.3
18 2026-08-27 05:47 639234055548642997
279 ms 121.162.154.3
17 2026-08-27 05:30 639234045267979603
582 ms 121.162.154.3
16 2026-08-27 05:13 639234034999717463
582 ms 121.162.154.3
15 2026-08-27 04:55 639234024739225358
602 ms 121.162.154.3
14 2026-08-27 04:38 639234014311170162
577 ms 121.162.154.3
13 2026-08-27 04:21 639234003806017640
588 ms 121.162.154.3
12 2026-08-27 04:03 639233993356203030
275 ms 121.162.154.3
11 2026-08-27 03:10 639233961301716608
574 ms 121.162.154.3
10 2026-08-27 02:53 639233950834200647
567 ms 121.162.154.3
9 2026-08-27 02:35 639233940431849026
585 ms 121.162.154.3
8 2026-08-27 02:18 639233930110596398
616 ms 121.162.154.3
7 2026-08-27 02:01 639233919705434540
576 ms 121.162.154.3
6 2026-08-27 01:43 639233909452807845
588 ms 121.162.154.3
5 2026-08-27 01:26 639233899096420820
595 ms 121.162.154.3
4 2026-08-27 01:09 639233888707824939
570 ms 121.162.154.3
3 2026-08-27 00:52 639233878461203802
589 ms 121.162.154.3
2 2026-08-27 00:34 639233868060868209
591 ms 121.162.154.3
1 2026-08-27 00:17 639233857450922991
609 ms 121.162.154.3