DNS response history for ns1.cbd.ryukyu

ns1.cbd.ryukyu 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 29 DNS check records, 29 successful responses, 0 failed responses, and 581 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.cbd.ryukyu.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

581 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

160.86.108.50

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns1.cbd.ryukyu

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
29 2026-08-26 09:16 639233318749762337
2233 ms 160.86.108.50
28 2026-08-26 08:58 639233308387917838
461 ms 160.86.108.50
27 2026-08-26 08:41 639233297961740122
453 ms 160.86.108.50
26 2026-08-26 08:23 639233287487159094
465 ms 160.86.108.50
25 2026-08-26 08:06 639233276995531707
469 ms 160.86.108.50
24 2026-08-26 07:48 639233266521568229
2040 ms 160.86.108.50
23 2026-08-26 07:31 639233256081047431
303 ms 160.86.108.50
22 2026-08-26 06:37 639233223620132921
457 ms 160.86.108.50
21 2026-08-26 06:20 639233213287814244
4 ms 160.86.108.50
20 2026-08-26 06:02 639233202925983161
435 ms 160.86.108.50
19 2026-08-26 05:45 639233192644780696
253 ms 160.86.108.50
18 2026-08-26 05:28 639233182401183833
4 ms 160.86.108.50
17 2026-08-26 05:11 639233172074181051
461 ms 160.86.108.50
16 2026-08-26 04:54 639233161808421455
449 ms 160.86.108.50
15 2026-08-26 04:37 639233151357344052
2245 ms 160.86.108.50
14 2026-08-26 04:19 639233141034116946
254 ms 160.86.108.50
13 2026-08-26 04:02 639233130828334142
463 ms 160.86.108.50
12 2026-08-26 03:45 639233120373450007
467 ms 160.86.108.50
11 2026-08-26 03:28 639233110066216193
7 ms 160.86.108.50
10 2026-08-26 02:34 639233078065410564
442 ms 160.86.108.50
9 2026-08-26 02:17 639233067787457832
230 ms 160.86.108.50
8 2026-08-26 02:00 639233057501801162
458 ms 160.86.108.50
7 2026-08-26 01:43 639233047089431703
441 ms 160.86.108.50
6 2026-08-26 01:25 639233036754790688
446 ms 160.86.108.50
5 2026-08-26 01:08 639233026412602472
441 ms 160.86.108.50
4 2026-08-26 00:51 639233016064066127
7 ms 160.86.108.50
3 2026-08-26 00:34 639233005922655772
460 ms 160.86.108.50
2 2026-08-26 00:17 639232995672256907
2007 ms 160.86.108.50
1 2026-08-26 00:00 639232985300872416
5 ms 160.86.108.50