DNS response history for ns3.leeboyeong.co.kr

ns3.leeboyeong.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 28 DNS check records, 28 successful responses, 0 failed responses, and 544 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 ns3.leeboyeong.co.kr.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

544 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.126.143.225

Most recently resolved hosting IP on selected date

Successful Responses

28

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 ns3.leeboyeong.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
28 2026-08-24 11:53 639231683712487276
578 ms 116.126.143.225
27 2026-08-24 11:36 639231673513573868
621 ms 116.126.143.225
26 2026-08-24 10:43 639231641791249939
569 ms 116.126.143.225
25 2026-08-24 10:26 639231631866211033
563 ms 116.126.143.225
24 2026-08-24 10:10 639231621644955316
553 ms 116.126.143.225
23 2026-08-24 09:53 639231611478799259
586 ms 116.126.143.225
22 2026-08-24 09:00 639231579923718211
611 ms 116.126.143.225
21 2026-08-24 08:43 639231569810702936
575 ms 116.126.143.225
20 2026-08-24 08:26 639231559762411619
579 ms 116.126.143.225
19 2026-08-24 08:09 639231549663595407
311 ms 116.126.143.225
18 2026-08-24 07:17 639231518076817246
808 ms 116.126.143.225
17 2026-08-24 07:00 639231508078650885
559 ms 116.126.143.225
16 2026-08-24 06:44 639231498210697093
582 ms 116.126.143.225
15 2026-08-24 06:27 639231488109699360
320 ms 116.126.143.225
14 2026-08-24 05:35 639231456772510692
566 ms 116.126.143.225
13 2026-08-24 05:18 639231447084631185
572 ms 116.126.143.225
12 2026-08-24 05:02 639231437208519473
3 ms 116.126.143.225
11 2026-08-24 04:45 639231427209627490
565 ms 116.126.143.225
10 2026-08-24 03:53 639231395791246644
804 ms 116.126.143.225
9 2026-08-24 03:37 639231386075551458
606 ms 116.126.143.225
8 2026-08-24 03:20 639231376208713791
563 ms 116.126.143.225
7 2026-08-24 03:04 639231366170589276
602 ms 116.126.143.225
6 2026-08-24 02:11 639231334732159368
276 ms 116.126.143.225
5 2026-08-24 01:55 639231325035670078
578 ms 116.126.143.225
4 2026-08-24 01:39 639231315132253837
596 ms 116.126.143.225
3 2026-08-24 01:22 639231305014280808
859 ms 116.126.143.225
2 2026-08-24 00:29 639231273779380675
811 ms 116.126.143.225
1 2026-08-24 00:13 639231264180839154
22 ms 116.126.143.225