DNS response history for ns2.amenews.kr

ns2.amenews.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 34 DNS check records, 34 successful responses, 0 failed responses, and 746 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.amenews.kr.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

746 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.126.85.98

Most recently resolved hosting IP on selected date

Successful Responses

34

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.amenews.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
34 2026-08-24 14:11 639231765923559455
606 ms 116.126.85.98
33 2026-08-24 13:54 639231755868832964
2283 ms 116.126.85.98
32 2026-08-24 13:37 639231745628278877
596 ms 116.126.85.98
31 2026-08-24 13:20 639231735407682062
5 ms 116.126.85.98
30 2026-08-24 12:27 639231703815441688
589 ms 116.126.85.98
29 2026-08-24 12:11 639231693747052549
618 ms 116.126.85.98
28 2026-08-24 11:54 639231683712487276
589 ms 116.126.85.98
27 2026-08-24 11:37 639231673513573868
603 ms 116.126.85.98
26 2026-08-24 10:44 639231641791249939
581 ms 116.126.85.98
25 2026-08-24 10:27 639231631866211033
585 ms 116.126.85.98
24 2026-08-24 10:11 639231621644955316
624 ms 116.126.85.98
23 2026-08-24 09:54 639231611478799259
2279 ms 116.126.85.98
22 2026-08-24 09:01 639231579923718211
852 ms 116.126.85.98
21 2026-08-24 08:44 639231569810702936
2291 ms 116.126.85.98
20 2026-08-24 08:27 639231559762411619
642 ms 116.126.85.98
19 2026-08-24 08:10 639231549663595407
603 ms 116.126.85.98
18 2026-08-24 07:17 639231518076817246
3 ms 116.126.85.98
17 2026-08-24 07:01 639231508078650885
268 ms 116.126.85.98
16 2026-08-24 06:44 639231498210697093
2266 ms 116.126.85.98
15 2026-08-24 06:28 639231488109699360
614 ms 116.126.85.98
14 2026-08-24 05:35 639231456772510692
8 ms 116.126.85.98
13 2026-08-24 05:19 639231447084631185
2 ms 116.126.85.98
12 2026-08-24 05:03 639231437208519473
604 ms 116.126.85.98
11 2026-08-24 04:46 639231427209627490
619 ms 116.126.85.98
10 2026-08-24 03:53 639231395791246644
1342 ms 116.126.85.98
9 2026-08-24 03:37 639231386075551458
2279 ms 116.126.85.98
8 2026-08-24 03:21 639231376208713791
283 ms 116.126.85.98
7 2026-08-24 03:05 639231366170589276
930 ms 116.126.85.98
6 2026-08-24 02:12 639231334732159368
3 ms 116.126.85.98
5 2026-08-24 01:56 639231325035670078
600 ms 116.126.85.98
4 2026-08-24 01:39 639231315132253837
3 ms 116.126.85.98
3 2026-08-24 01:23 639231305014280808
617 ms 116.126.85.98
2 2026-08-24 00:30 639231273779380675
2 ms 116.126.85.98
1 2026-08-24 00:14 639231264180839154
588 ms 116.126.85.98