DNS response history for ns.jp.go.kr

ns.jp.go.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 36 DNS check records, 34 successful responses, 2 failed responses, and 2319 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.jp.go.kr.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

2319 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

27.101.146.102

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

6%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns.jp.go.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
36 2026-08-26 12:00 639233414056832719
294 ms 27.101.146.102
35 2026-08-26 11:42 639233403515141099
3510 ms 27.101.146.102
34 2026-08-26 10:47 639233370841350248
295 ms 27.101.146.102
33 2026-08-26 10:30 639233360361507238
2008 ms 27.101.146.102
32 2026-08-26 10:13 639233350067824371
3785 ms 27.101.146.102
31 2026-08-26 09:56 639233339545274518
3787 ms 27.101.146.102
30 2026-08-26 09:38 639233329214918079
3510 ms 27.101.146.102
29 2026-08-26 09:21 639233318749762337
294 ms 27.101.146.102
28 2026-08-26 09:03 639233308387917838
2277 ms 27.101.146.102
27 2026-08-26 08:46 639233297961740122
3508 ms 27.101.146.102
26 2026-08-26 08:29 639233287487159094
3781 ms 27.101.146.102
25 2026-08-26 08:11 639233276995531707
4001 ms 27.101.146.102
24 2026-08-26 07:54 639233266521568229
3781 ms 27.101.146.102
23 2026-08-26 07:36 639233256081047431
-
22 2026-08-26 06:42 639233223620132921
3775 ms 27.101.146.102
21 2026-08-26 06:25 639233213287814244
2291 ms 27.101.146.102
20 2026-08-26 06:08 639233202925983161
3511 ms 27.101.146.102
19 2026-08-26 05:50 639233192644780696
3 ms 27.101.146.102
18 2026-08-26 05:33 639233182401183833
3787 ms 27.101.146.102
17 2026-08-26 05:16 639233172074181051
-
16 2026-08-26 04:59 639233161808421455
3800 ms 27.101.146.102
15 2026-08-26 04:42 639233151357344052
299 ms 27.101.146.102
14 2026-08-26 04:24 639233141034116946
2035 ms 27.101.146.102
13 2026-08-26 04:07 639233130828334142
3830 ms 27.101.146.102
12 2026-08-26 03:50 639233120373450007
2031 ms 27.101.146.102
11 2026-08-26 03:33 639233110066216193
2388 ms 27.101.146.102
10 2026-08-26 02:39 639233078065410564
2279 ms 27.101.146.102
9 2026-08-26 02:22 639233067787457832
287 ms 27.101.146.102
8 2026-08-26 02:05 639233057501801162
2009 ms 27.101.146.102
7 2026-08-26 01:48 639233047089431703
2 ms 27.101.146.102
6 2026-08-26 01:31 639233036754790688
3786 ms 27.101.146.102
5 2026-08-26 01:13 639233026412602472
291 ms 27.101.146.102
4 2026-08-26 00:56 639233016064066127
293 ms 27.101.146.102
3 2026-08-26 00:39 639233005922655772
2012 ms 27.101.146.102
2 2026-08-26 00:22 639232995672256907
2863 ms 27.101.146.102
1 2026-08-26 00:05 639232985300872416
2432 ms 27.101.146.102