DNS response history for ns.cherry.jp

ns.cherry.jp 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 33 DNS check records, 33 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 ns.cherry.jp.
Records on Selected Date

33

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 13:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.127.36.98

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns.cherry.jp

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
33 2026-08-24 13:54 639231755868832964
353 ms 153.127.36.98
32 2026-08-24 13:37 639231745628278877
558 ms 153.127.36.98
31 2026-08-24 13:20 639231735407682062
560 ms 153.127.36.98
30 2026-08-24 12:27 639231703815441688
3 ms 153.127.36.98
29 2026-08-24 12:10 639231693747052549
580 ms 153.127.36.98
28 2026-08-24 11:54 639231683712487276
568 ms 153.127.36.98
27 2026-08-24 11:37 639231673513573868
571 ms 153.127.36.98
26 2026-08-24 10:43 639231641791249939
555 ms 153.127.36.98
25 2026-08-24 10:27 639231631866211033
4007 ms 153.127.36.98
24 2026-08-24 10:10 639231621644955316
559 ms 153.127.36.98
23 2026-08-24 09:53 639231611478799259
599 ms 153.127.36.98
22 2026-08-24 09:01 639231579923718211
586 ms 153.127.36.98
21 2026-08-24 08:44 639231569810702936
634 ms 153.127.36.98
20 2026-08-24 08:27 639231559762411619
571 ms 153.127.36.98
19 2026-08-24 08:10 639231549663595407
592 ms 153.127.36.98
18 2026-08-24 07:17 639231518076817246
560 ms 153.127.36.98
17 2026-08-24 07:01 639231508078650885
585 ms 153.127.36.98
16 2026-08-24 06:44 639231498210697093
4 ms 153.127.36.98
15 2026-08-24 06:28 639231488109699360
577 ms 153.127.36.98
14 2026-08-24 05:35 639231456772510692
3 ms 153.127.36.98
13 2026-08-24 05:19 639231447084631185
587 ms 153.127.36.98
12 2026-08-24 05:02 639231437208519473
282 ms 153.127.36.98
11 2026-08-24 04:46 639231427209627490
564 ms 153.127.36.98
10 2026-08-24 03:53 639231395791246644
3 ms 153.127.36.98
9 2026-08-24 03:37 639231386075551458
573 ms 153.127.36.98
8 2026-08-24 03:21 639231376208713791
572 ms 153.127.36.98
7 2026-08-24 03:04 639231366170589276
590 ms 153.127.36.98
6 2026-08-24 02:12 639231334732159368
2 ms 153.127.36.98
5 2026-08-24 01:56 639231325035670078
3 ms 153.127.36.98
4 2026-08-24 01:39 639231315132253837
587 ms 153.127.36.98
3 2026-08-24 01:23 639231305014280808
573 ms 153.127.36.98
2 2026-08-24 00:30 639231273779380675
583 ms 153.127.36.98
1 2026-08-24 00:14 639231264180839154
4 ms 153.127.36.98