DNS response history for ns2.danyang.go.kr

ns2.danyang.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-25. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 947 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.danyang.go.kr.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

947 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

27.101.150.5

Most recently resolved hosting IP on selected date

Successful Responses

31

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

Showing DNS history for 2026-08-25 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
31 2026-08-25 10:22 639232492740373468
1452 ms 27.101.150.5
30 2026-08-25 10:05 639232482235303141
1178 ms 27.101.150.5
29 2026-08-25 09:48 639232471861770303
1174 ms 27.101.150.5
28 2026-08-25 09:30 639232461630217327
874 ms 27.101.150.5
27 2026-08-25 09:13 639232451282965990
1159 ms 27.101.150.5
26 2026-08-25 08:56 639232440814614938
1318 ms 27.101.150.5
25 2026-08-25 08:39 639232430410720425
1221 ms 27.101.150.5
24 2026-08-25 08:21 639232420003096185
1159 ms 27.101.150.5
23 2026-08-25 08:04 639232409467287444
297 ms 27.101.150.5
22 2026-08-25 07:46 639232399077195997
1176 ms 27.101.150.5
21 2026-08-25 07:29 639232388731528337
1194 ms 27.101.150.5
20 2026-08-25 07:12 639232378288598612
1184 ms 27.101.150.5
19 2026-08-25 06:18 639232346196373643
5 ms 27.101.150.5
18 2026-08-25 06:01 639232336112370741
3 ms 27.101.150.5
17 2026-08-25 05:44 639232326146508970
1193 ms 27.101.150.5
16 2026-08-25 05:28 639232316189381720
3 ms 27.101.150.5
15 2026-08-25 05:11 639232306217998913
2 ms 27.101.150.5
14 2026-08-25 04:55 639232296255744174
1182 ms 27.101.150.5
13 2026-08-25 04:38 639232286095760789
1179 ms 27.101.150.5
12 2026-08-25 04:21 639232276086186273
1193 ms 27.101.150.5
11 2026-08-25 04:04 639232265900986425
1170 ms 27.101.150.5
10 2026-08-25 03:47 639232255723518075
1167 ms 27.101.150.5
9 2026-08-25 03:30 639232245484452890
1166 ms 27.101.150.5
8 2026-08-25 03:13 639232235157175331
1165 ms 27.101.150.5
7 2026-08-25 02:20 639232203197189095
1195 ms 27.101.150.5
6 2026-08-25 02:03 639232192844564298
602 ms 27.101.150.5
5 2026-08-25 01:45 639232182496008942
1183 ms 27.101.150.5
4 2026-08-25 01:28 639232172197053132
4 ms 27.101.150.5
3 2026-08-25 00:35 639232140250307418
1185 ms 27.101.150.5
2 2026-08-25 00:18 639232129927860324
1193 ms 27.101.150.5
1 2026-08-25 00:00 639232119551972438
1182 ms 27.101.150.5