DNS response history for ns1.sho-jukukan.com

ns1.sho-jukukan.com 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 34 DNS check records, 33 successful responses, 1 failed responses, and 207 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 ns1.sho-jukukan.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

207 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

23.94.76.66

Most recently resolved hosting IP on selected date

Successful Responses

33

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.sho-jukukan.com

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
34 2026-08-24 14:05 639231765923559455
298 ms 23.94.76.66
33 2026-08-24 13:48 639231755868832964
156 ms 23.94.76.66
32 2026-08-24 13:31 639231745628278877
275 ms 23.94.76.66
31 2026-08-24 13:14 639231735407682062
247 ms 23.94.76.66
30 2026-08-24 12:21 639231703815441688
333 ms 23.94.76.66
29 2026-08-24 12:05 639231693747052549
237 ms 23.94.76.66
28 2026-08-24 11:48 639231683712487276
252 ms 23.94.76.66
27 2026-08-24 11:31 639231673513573868
265 ms 23.94.76.66
26 2026-08-24 10:38 639231641791249939
280 ms 23.94.76.66
25 2026-08-24 10:21 639231631866211033
328 ms 23.94.76.66
24 2026-08-24 10:04 639231621644955316
291 ms 23.94.76.66
23 2026-08-24 09:47 639231611478799259
336 ms 23.94.76.66
22 2026-08-24 08:55 639231579923718211
66 ms 23.94.76.66
21 2026-08-24 08:38 639231569810702936
332 ms 23.94.76.66
20 2026-08-24 08:21 639231559762411619
318 ms 23.94.76.66
19 2026-08-24 08:04 639231549663595407
259 ms 23.94.76.66
18 2026-08-24 07:12 639231518076817246
26 ms 23.94.76.66
17 2026-08-24 06:55 639231508078650885
284 ms 23.94.76.66
16 2026-08-24 06:39 639231498210697093
286 ms 23.94.76.66
15 2026-08-24 06:22 639231488109699360
229 ms 23.94.76.66
14 2026-08-24 05:30 639231456772510692
133 ms 23.94.76.66
13 2026-08-24 05:14 639231447084631185
288 ms 23.94.76.66
12 2026-08-24 04:57 639231437208519473
26 ms 23.94.76.66
11 2026-08-24 04:40 639231427209627490
233 ms 23.94.76.66
10 2026-08-24 03:48 639231395791246644
-
9 2026-08-24 03:32 639231386075551458
38 ms 23.94.76.66
8 2026-08-24 03:15 639231376208713791
57 ms 23.94.76.66
7 2026-08-24 02:59 639231366170589276
232 ms 23.94.76.66
6 2026-08-24 02:06 639231334732159368
103 ms 23.94.76.66
5 2026-08-24 01:50 639231325035670078
19 ms 23.94.76.66
4 2026-08-24 01:34 639231315132253837
296 ms 23.94.76.66
3 2026-08-24 01:17 639231305014280808
226 ms 23.94.76.66
2 2026-08-24 00:25 639231273779380675
23 ms 23.94.76.66
1 2026-08-24 00:09 639231264180839154
55 ms 23.94.76.66