DNS response history for ns3.jbdry.co.kr

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

36

Historical checks stored for this nameserver on selected date

Average Latency

618 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:21

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

36

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.jbdry.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
36 2026-08-24 15:21 639231807961539652
2 ms 116.126.143.225
35 2026-08-24 15:04 639231797631669865
596 ms 116.126.143.225
34 2026-08-24 14:10 639231765923559455
771 ms 116.126.143.225
33 2026-08-24 13:54 639231755868832964
650 ms 116.126.143.225
32 2026-08-24 13:37 639231745628278877
590 ms 116.126.143.225
31 2026-08-24 13:20 639231735407682062
460 ms 116.126.143.225
30 2026-08-24 12:27 639231703815441688
443 ms 116.126.143.225
29 2026-08-24 12:10 639231693747052549
580 ms 116.126.143.225
28 2026-08-24 11:53 639231683712487276
618 ms 116.126.143.225
27 2026-08-24 11:37 639231673513573868
895 ms 116.126.143.225
26 2026-08-24 10:43 639231641791249939
760 ms 116.126.143.225
25 2026-08-24 10:27 639231631866211033
578 ms 116.126.143.225
24 2026-08-24 10:10 639231621644955316
316 ms 116.126.143.225
23 2026-08-24 09:53 639231611478799259
1006 ms 116.126.143.225
22 2026-08-24 09:00 639231579923718211
570 ms 116.126.143.225
21 2026-08-24 08:44 639231569810702936
844 ms 116.126.143.225
20 2026-08-24 08:27 639231559762411619
555 ms 116.126.143.225
19 2026-08-24 08:10 639231549663595407
872 ms 116.126.143.225
18 2026-08-24 07:17 639231518076817246
734 ms 116.126.143.225
17 2026-08-24 07:01 639231508078650885
646 ms 116.126.143.225
16 2026-08-24 06:44 639231498210697093
1079 ms 116.126.143.225
15 2026-08-24 06:27 639231488109699360
584 ms 116.126.143.225
14 2026-08-24 05:35 639231456772510692
3 ms 116.126.143.225
13 2026-08-24 05:19 639231447084631185
608 ms 116.126.143.225
12 2026-08-24 05:02 639231437208519473
657 ms 116.126.143.225
11 2026-08-24 04:46 639231427209627490
601 ms 116.126.143.225
10 2026-08-24 03:53 639231395791246644
1200 ms 116.126.143.225
9 2026-08-24 03:37 639231386075551458
756 ms 116.126.143.225
8 2026-08-24 03:21 639231376208713791
3 ms 116.126.143.225
7 2026-08-24 03:04 639231366170589276
956 ms 116.126.143.225
6 2026-08-24 02:12 639231334732159368
3 ms 116.126.143.225
5 2026-08-24 01:55 639231325035670078
773 ms 116.126.143.225
4 2026-08-24 01:39 639231315132253837
3 ms 116.126.143.225
3 2026-08-24 01:22 639231305014280808
904 ms 116.126.143.225
2 2026-08-24 00:30 639231273779380675
880 ms 116.126.143.225
1 2026-08-24 00:14 639231264180839154
744 ms 116.126.143.225