DNS response history for ns2.nexus.pe.kr

ns2.nexus.pe.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 388 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.nexus.pe.kr.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

388 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.38.194.58

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.nexus.pe.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:10 639231765923559455
900 ms 61.38.194.58
33 2026-08-24 13:53 639231755868832964
8 ms 61.38.194.58
32 2026-08-24 13:36 639231745628278877
6 ms 61.38.194.58
31 2026-08-24 13:19 639231735407682062
593 ms 61.38.194.58
30 2026-08-24 12:26 639231703815441688
609 ms 61.38.194.58
29 2026-08-24 12:10 639231693747052549
605 ms 61.38.194.58
28 2026-08-24 11:53 639231683712487276
3 ms 61.38.194.58
27 2026-08-24 11:36 639231673513573868
5 ms 61.38.194.58
26 2026-08-24 10:43 639231641791249939
7 ms 61.38.194.58
25 2026-08-24 10:26 639231631866211033
5 ms 61.38.194.58
24 2026-08-24 10:10 639231621644955316
617 ms 61.38.194.58
23 2026-08-24 09:53 639231611478799259
309 ms 61.38.194.58
22 2026-08-24 09:00 639231579923718211
4 ms 61.38.194.58
21 2026-08-24 08:43 639231569810702936
602 ms 61.38.194.58
20 2026-08-24 08:26 639231559762411619
639 ms 61.38.194.58
19 2026-08-24 08:09 639231549663595407
3 ms 61.38.194.58
18 2026-08-24 07:17 639231518076817246
4 ms 61.38.194.58
17 2026-08-24 07:00 639231508078650885
606 ms 61.38.194.58
16 2026-08-24 06:43 639231498210697093
598 ms 61.38.194.58
15 2026-08-24 06:27 639231488109699360
622 ms 61.38.194.58
14 2026-08-24 05:35 639231456772510692
3 ms 61.38.194.58
13 2026-08-24 05:18 639231447084631185
2 ms 61.38.194.58
12 2026-08-24 05:02 639231437208519473
3 ms 61.38.194.58
11 2026-08-24 04:45 639231427209627490
3 ms 61.38.194.58
10 2026-08-24 03:53 639231395791246644
613 ms 61.38.194.58
9 2026-08-24 03:37 639231386075551458
625 ms 61.38.194.58
8 2026-08-24 03:20 639231376208713791
2266 ms 61.38.194.58
7 2026-08-24 03:04 639231366170589276
606 ms 61.38.194.58
6 2026-08-24 02:11 639231334732159368
2303 ms 61.38.194.58
5 2026-08-24 01:55 639231325035670078
3 ms 61.38.194.58
4 2026-08-24 01:39 639231315132253837
3 ms 61.38.194.58
3 2026-08-24 01:22 639231305014280808
3 ms 61.38.194.58
2 2026-08-24 00:29 639231273779380675
4 ms 61.38.194.58
1 2026-08-24 00:13 639231264180839154
4 ms 61.38.194.58