DNS response history for ns1.sejong.go.kr

ns1.sejong.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 30 DNS check records, 30 successful responses, 0 failed responses, and 962 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.sejong.go.kr.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

962 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

27.101.58.1

Most recently resolved hosting IP on selected date

Successful Responses

30

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.sejong.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
30 2026-08-24 12:27 639231703815441688
915 ms 27.101.58.1
29 2026-08-24 12:11 639231693747052549
1141 ms 27.101.58.1
28 2026-08-24 11:54 639231683712487276
903 ms 27.101.58.1
27 2026-08-24 11:37 639231673513573868
905 ms 27.101.58.1
26 2026-08-24 10:44 639231641791249939
882 ms 27.101.58.1
25 2026-08-24 10:27 639231631866211033
902 ms 27.101.58.1
24 2026-08-24 10:11 639231621644955316
1156 ms 27.101.58.1
23 2026-08-24 09:54 639231611478799259
903 ms 27.101.58.1
22 2026-08-24 09:01 639231579923718211
938 ms 27.101.58.1
21 2026-08-24 08:44 639231569810702936
1379 ms 27.101.58.1
20 2026-08-24 08:27 639231559762411619
1645 ms 27.101.58.1
19 2026-08-24 08:11 639231549663595407
903 ms 27.101.58.1
18 2026-08-24 07:18 639231518076817246
889 ms 27.101.58.1
17 2026-08-24 07:01 639231508078650885
889 ms 27.101.58.1
16 2026-08-24 06:45 639231498210697093
909 ms 27.101.58.1
15 2026-08-24 06:28 639231488109699360
910 ms 27.101.58.1
14 2026-08-24 05:36 639231456772510692
918 ms 27.101.58.1
13 2026-08-24 05:19 639231447084631185
892 ms 27.101.58.1
12 2026-08-24 05:03 639231437208519473
914 ms 27.101.58.1
11 2026-08-24 04:46 639231427209627490
893 ms 27.101.58.1
10 2026-08-24 03:54 639231395791246644
922 ms 27.101.58.1
9 2026-08-24 03:38 639231386075551458
889 ms 27.101.58.1
8 2026-08-24 03:21 639231376208713791
888 ms 27.101.58.1
7 2026-08-24 03:05 639231366170589276
881 ms 27.101.58.1
6 2026-08-24 02:12 639231334732159368
904 ms 27.101.58.1
5 2026-08-24 01:56 639231325035670078
895 ms 27.101.58.1
4 2026-08-24 01:40 639231315132253837
901 ms 27.101.58.1
3 2026-08-24 01:23 639231305014280808
905 ms 27.101.58.1
2 2026-08-24 00:30 639231273779380675
899 ms 27.101.58.1
1 2026-08-24 00:14 639231264180839154
977 ms 27.101.58.1