DNS response history for ns1.seongnam.go.kr

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

32

Historical checks stored for this nameserver on selected date

Average Latency

494 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

27.101.102.1

Most recently resolved hosting IP on selected date

Successful Responses

32

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.seongnam.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
32 2026-08-24 13:36 639231745628278877
590 ms 27.101.102.1
31 2026-08-24 13:19 639231735407682062
591 ms 27.101.102.1
30 2026-08-24 12:26 639231703815441688
595 ms 27.101.102.1
29 2026-08-24 12:10 639231693747052549
2363 ms 27.101.102.1
28 2026-08-24 11:53 639231683712487276
598 ms 27.101.102.1
27 2026-08-24 11:36 639231673513573868
595 ms 27.101.102.1
26 2026-08-24 10:43 639231641791249939
286 ms 27.101.102.1
25 2026-08-24 10:27 639231631866211033
578 ms 27.101.102.1
24 2026-08-24 10:10 639231621644955316
572 ms 27.101.102.1
23 2026-08-24 09:53 639231611478799259
593 ms 27.101.102.1
22 2026-08-24 09:00 639231579923718211
5 ms 27.101.102.1
21 2026-08-24 08:43 639231569810702936
616 ms 27.101.102.1
20 2026-08-24 08:26 639231559762411619
459 ms 27.101.102.1
19 2026-08-24 08:10 639231549663595407
610 ms 27.101.102.1
18 2026-08-24 07:17 639231518076817246
3 ms 27.101.102.1
17 2026-08-24 07:00 639231508078650885
605 ms 27.101.102.1
16 2026-08-24 06:44 639231498210697093
5 ms 27.101.102.1
15 2026-08-24 06:27 639231488109699360
587 ms 27.101.102.1
14 2026-08-24 05:35 639231456772510692
4 ms 27.101.102.1
13 2026-08-24 05:18 639231447084631185
633 ms 27.101.102.1
12 2026-08-24 05:02 639231437208519473
592 ms 27.101.102.1
11 2026-08-24 04:45 639231427209627490
3 ms 27.101.102.1
10 2026-08-24 03:53 639231395791246644
572 ms 27.101.102.1
9 2026-08-24 03:37 639231386075551458
3 ms 27.101.102.1
8 2026-08-24 03:20 639231376208713791
577 ms 27.101.102.1
7 2026-08-24 03:04 639231366170589276
292 ms 27.101.102.1
6 2026-08-24 02:11 639231334732159368
631 ms 27.101.102.1
5 2026-08-24 01:55 639231325035670078
698 ms 27.101.102.1
4 2026-08-24 01:39 639231315132253837
752 ms 27.101.102.1
3 2026-08-24 01:22 639231305014280808
359 ms 27.101.102.1
2 2026-08-24 00:29 639231273779380675
3 ms 27.101.102.1
1 2026-08-24 00:14 639231264180839154
427 ms 27.101.102.1