DNS response history for ns.accessto.co.kr

ns.accessto.co.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, 27 successful responses, 0 failed responses, and 1180 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 ns.accessto.co.kr.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

1180 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

61.78.63.157

Most recently resolved hosting IP on selected date

Successful Responses

27

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 ns.accessto.co.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
1768 ms 61.78.63.157
26 2026-08-24 10:44 639231641791249939
4 ms 61.78.63.157
25 2026-08-24 10:28 639231631866211033
1737 ms 61.78.63.157
24 2026-08-24 10:11 639231621644955316
1739 ms 61.78.63.157
23 2026-08-24 09:54 639231611478799259
1738 ms 61.78.63.157
22 2026-08-24 09:01 639231579923718211
329 ms 61.78.63.157
21 2026-08-24 08:45 639231569810702936
1743 ms 61.78.63.157
20 2026-08-24 08:28 639231559762411619
1749 ms 61.78.63.157
19 2026-08-24 08:11 639231549663595407
1737 ms 61.78.63.157
18 2026-08-24 07:18 639231518076817246
1736 ms 61.78.63.157
17 2026-08-24 07:02 639231508078650885
1736 ms 61.78.63.157
16 2026-08-24 06:45 639231498210697093
1758 ms 61.78.63.157
15 2026-08-24 06:29 639231488109699360
1786 ms 61.78.63.157
14 2026-08-24 05:36 639231456772510692
1743 ms 61.78.63.157
13 2026-08-24 05:20 639231447084631185
3 ms 61.78.63.157
12 2026-08-24 05:03 639231437208519473
2 ms 61.78.63.157
11 2026-08-24 04:47 639231427209627490
1755 ms 61.78.63.157
10 2026-08-24 03:54 639231395791246644
2 ms 61.78.63.157
9 2026-08-24 03:38 639231386075551458
3 ms 61.78.63.157
8 2026-08-24 03:22 639231376208713791
1786 ms 61.78.63.157
7 2026-08-24 03:05 639231366170589276
1177 ms 61.78.63.157
6 2026-08-24 02:13 639231334732159368
3 ms 61.78.63.157
5 2026-08-24 01:56 639231325035670078
1773 ms 61.78.63.157
4 2026-08-24 01:40 639231315132253837
549 ms 61.78.63.157
3 2026-08-24 01:23 639231305014280808
1739 ms 61.78.63.157
2 2026-08-24 00:31 639231273779380675
4 ms 61.78.63.157
1 2026-08-24 00:15 639231264180839154
1756 ms 61.78.63.157