DNS response history for ns1.seocheon.go.kr

ns1.seocheon.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 27 DNS check records, 26 successful responses, 1 failed responses, and 853 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.seocheon.go.kr.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

853 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

27.101.60.140

Most recently resolved hosting IP on selected date

Successful Responses

26

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.seocheon.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
27 2026-08-24 11:38 639231673513573868
2289 ms 27.101.60.140
26 2026-08-24 10:44 639231641791249939
2008 ms 27.101.60.140
25 2026-08-24 10:28 639231631866211033
295 ms 27.101.60.140
24 2026-08-24 10:11 639231621644955316
2276 ms 27.101.60.140
23 2026-08-24 09:54 639231611478799259
4 ms 27.101.60.140
22 2026-08-24 09:01 639231579923718211
3 ms 27.101.60.140
21 2026-08-24 08:45 639231569810702936
5 ms 27.101.60.140
20 2026-08-24 08:28 639231559762411619
6 ms 27.101.60.140
19 2026-08-24 08:11 639231549663595407
4306 ms 27.101.60.140
18 2026-08-24 07:18 639231518076817246
2 ms 27.101.60.140
17 2026-08-24 07:02 639231508078650885
2576 ms 27.101.60.140
16 2026-08-24 06:45 639231498210697093
4 ms 27.101.60.140
15 2026-08-24 06:29 639231488109699360
-
14 2026-08-24 05:36 639231456772510692
2 ms 27.101.60.140
13 2026-08-24 05:20 639231447084631185
3 ms 27.101.60.140
12 2026-08-24 05:03 639231437208519473
3 ms 27.101.60.140
11 2026-08-24 04:47 639231427209627490
3113 ms 27.101.60.140
10 2026-08-24 03:54 639231395791246644
2 ms 27.101.60.140
9 2026-08-24 03:38 639231386075551458
3 ms 27.101.60.140
8 2026-08-24 03:22 639231376208713791
9 ms 27.101.60.140
7 2026-08-24 03:05 639231366170589276
2009 ms 27.101.60.140
6 2026-08-24 02:13 639231334732159368
3 ms 27.101.60.140
5 2026-08-24 01:56 639231325035670078
3 ms 27.101.60.140
4 2026-08-24 01:40 639231315132253837
3238 ms 27.101.60.140
3 2026-08-24 01:23 639231305014280808
3 ms 27.101.60.140
2 2026-08-24 00:31 639231273779380675
4 ms 27.101.60.140
1 2026-08-24 00:15 639231264180839154
3 ms 27.101.60.140