bgpreport

Network · data from 2026-11-12

AS25846 US-CLOUDNIUM-01

Registry name: US-CLOUDNIUM-01 - Cloudnium LLC, US · PeeringDB

12IPv4 routes 83.3% RPKI valid · 83.3% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS25846, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS25846, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
154.17.254.0/24 No ROA None 673 100% 67
38.183.210.0/24 No ROA None 672 100% 67
185.126.181.0/24 Valid Other IRR onlyRADB 671 100% 67
2602:fed2:770a::/48 Valid Other IRR onlyRADB 636 100% 67
140.228.20.0/24 Valid RIR databaseARIN, RADB 673 100% 67
180.149.32.0/24 Valid RIR databaseARIN, RADB 673 100% 67
104.234.254.0/24 Valid RIR databaseARIN, RADB 671 100% 67
107.149.29.0/24 Valid RIR databaseARIN, RADB 671 100% 67
139.177.151.0/24 Valid RIR databaseARIN, RADB 671 100% 67
144.225.86.0/24 Valid RIR databaseARIN, RADB 671 100% 67
157.254.188.0/24 Valid RIR databaseARIN, RADB 671 100% 67
185.126.158.0/23 Valid RIR databaseRADB, RIPE 671 100% 67
205.186.71.0/24 Valid RIR databaseARIN, RADB 671 100% 67
2602:f3f0:100::/40 Valid RIR databaseARIN, RADB 635 100% 67

AS-SET

AS25846's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 11 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none154.17.254.0/24No ROA covers it. Add a ROA for AS25846, maxLength 24.673 of 673
Route object: none154.17.254.0/24No route object for it. Add a route object with origin AS25846 in the RIR database for the space.673 of 673
ROA: none38.183.210.0/24No ROA covers it. Add a ROA for AS25846, maxLength 24.672 of 673
Route object: none38.183.210.0/24No route object for it. Add a route object with origin AS25846 in the RIR database for the space.672 of 673
Route object: RIR185.126.181.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2602:fed2:770a::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

Route objects with origin AS25846 whose prefix no peer sees AS25846 announce. Many are kept on purpose (backup routes, space announced only in some places).

23.173.216.0/24ARINValid
103.172.134.0/24APNICValid
103.172.135.0/24APNICValid
2407:d340::/32APNICValid
2602:f947::/40ARINValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.