DNS response history for ns2.yuseong.go.kr

ns2.yuseong.go.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-24. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 358 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.yuseong.go.kr.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

358 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

27.101.69.15

Most recently resolved hosting IP on selected date

Successful Responses

26

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.yuseong.go.kr

Showing DNS history for 2026-08-24 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
26 2026-08-24 10:43 639231641791249939
3 ms 27.101.69.15
25 2026-08-24 10:26 639231631866211033
5 ms 27.101.69.15
24 2026-08-24 10:10 639231621644955316
4 ms 27.101.69.15
23 2026-08-24 09:53 639231611478799259
585 ms 27.101.69.15
22 2026-08-24 09:00 639231579923718211
593 ms 27.101.69.15
21 2026-08-24 08:43 639231569810702936
6 ms 27.101.69.15
20 2026-08-24 08:26 639231559762411619
484 ms 27.101.69.15
19 2026-08-24 08:10 639231549663595407
582 ms 27.101.69.15
18 2026-08-24 07:17 639231518076817246
3 ms 27.101.69.15
17 2026-08-24 07:00 639231508078650885
3 ms 27.101.69.15
16 2026-08-24 06:44 639231498210697093
578 ms 27.101.69.15
15 2026-08-24 06:27 639231488109699360
611 ms 27.101.69.15
14 2026-08-24 05:35 639231456772510692
2 ms 27.101.69.15
13 2026-08-24 05:18 639231447084631185
822 ms 27.101.69.15
12 2026-08-24 05:02 639231437208519473
278 ms 27.101.69.15
11 2026-08-24 04:45 639231427209627490
573 ms 27.101.69.15
10 2026-08-24 03:53 639231395791246644
2 ms 27.101.69.15
9 2026-08-24 03:37 639231386075551458
584 ms 27.101.69.15
8 2026-08-24 03:20 639231376208713791
586 ms 27.101.69.15
7 2026-08-24 03:04 639231366170589276
571 ms 27.101.69.15
6 2026-08-24 02:11 639231334732159368
587 ms 27.101.69.15
5 2026-08-24 01:55 639231325035670078
3 ms 27.101.69.15
4 2026-08-24 01:39 639231315132253837
588 ms 27.101.69.15
3 2026-08-24 01:22 639231305014280808
615 ms 27.101.69.15
2 2026-08-24 00:29 639231273779380675
582 ms 27.101.69.15
1 2026-08-24 00:14 639231264180839154
67 ms 27.101.69.15