DNS response history for ns2.jbedu.or.kr

ns2.jbedu.or.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-26. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 1641 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.jbedu.or.kr.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

1641 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.126.106.3

Most recently resolved hosting IP on selected date

Successful Responses

31

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.jbedu.or.kr

Showing DNS history for 2026-08-26 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
31 2026-08-26 09:55 639233339545274518
4549 ms 116.126.106.3
30 2026-08-26 09:37 639233329214918079
1231 ms 116.126.106.3
29 2026-08-26 09:20 639233318749762337
1743 ms 116.126.106.3
28 2026-08-26 09:03 639233308387917838
2841 ms 116.126.106.3
27 2026-08-26 08:46 639233297961740122
1982 ms 116.126.106.3
26 2026-08-26 08:28 639233287487159094
1999 ms 116.126.106.3
25 2026-08-26 08:11 639233276995531707
1759 ms 116.126.106.3
24 2026-08-26 07:53 639233266521568229
1751 ms 116.126.106.3
23 2026-08-26 07:36 639233256081047431
1176 ms 116.126.106.3
22 2026-08-26 06:42 639233223620132921
1780 ms 116.126.106.3
21 2026-08-26 06:24 639233213287814244
1766 ms 116.126.106.3
20 2026-08-26 06:07 639233202925983161
1767 ms 116.126.106.3
19 2026-08-26 05:50 639233192644780696
5 ms 116.126.106.3
18 2026-08-26 05:33 639233182401183833
1771 ms 116.126.106.3
17 2026-08-26 05:16 639233172074181051
1767 ms 116.126.106.3
16 2026-08-26 04:58 639233161808421455
1763 ms 116.126.106.3
15 2026-08-26 04:41 639233151357344052
1198 ms 116.126.106.3
14 2026-08-26 04:24 639233141034116946
1757 ms 116.126.106.3
13 2026-08-26 04:07 639233130828334142
1767 ms 116.126.106.3
12 2026-08-26 03:49 639233120373450007
4 ms 116.126.106.3
11 2026-08-26 03:32 639233110066216193
1768 ms 116.126.106.3
10 2026-08-26 02:39 639233078065410564
1259 ms 116.126.106.3
9 2026-08-26 02:22 639233067787457832
2 ms 116.126.106.3
8 2026-08-26 02:05 639233057501801162
1759 ms 116.126.106.3
7 2026-08-26 01:47 639233047089431703
1755 ms 116.126.106.3
6 2026-08-26 01:30 639233036754790688
1736 ms 116.126.106.3
5 2026-08-26 01:13 639233026412602472
1773 ms 116.126.106.3
4 2026-08-26 00:56 639233016064066127
1757 ms 116.126.106.3
3 2026-08-26 00:38 639233005922655772
1194 ms 116.126.106.3
2 2026-08-26 00:21 639232995672256907
1741 ms 116.126.106.3
1 2026-08-26 00:04 639232985300872416
1752 ms 116.126.106.3