bgpreport

Network · data from 2026-11-12

AS20333 OPSUS-NET - Cloudwave

Registry name: OPSUS-NET - Cloudwave, US · not in PeeringDB

8IPv4 routes 0.0% RPKI valid · 25.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
8No ROA 6 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS20333, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS20333, 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.

104.36.160.0/24 No ROA Nonecovered by 104.36.160.0/23 673 100% 67
104.36.161.0/24 No ROA Nonecovered by 104.36.160.0/23 673 100% 67
206.198.136.0/24 No ROA Nonecovered by 206.198.136.0/21 673 100% 67
206.198.137.0/24 No ROA Nonecovered by 206.198.136.0/21 673 100% 67
206.198.138.0/24 No ROA Nonecovered by 206.198.136.0/21 673 100% 67
206.198.139.0/24 No ROA Nonecovered by 206.198.136.0/21 673 100% 67
199.89.51.0/24 No ROA Other IRR onlyALTDB 673 100% 67
207.67.99.0/24 No ROA Other IRR onlyALTDB, RADB 673 100% 67

AS-SET

AS20333 isn't in PeeringDB, where networks name their 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 20 are in fix.csv.

  • ROA: none8
  • Route object: none6
  • Route object: RIR2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none104.36.160.0/24No ROA covers it. Add a ROA for AS20333, maxLength 24.673 of 673
Route object: none104.36.160.0/24No route object for it. A route object for 104.36.160.0/23 with origin AS20333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20333 in the RIR database for the space.673 of 673
ROA: none104.36.161.0/24No ROA covers it. Add a ROA for AS20333, maxLength 24.673 of 673
Route object: none104.36.161.0/24No route object for it. A route object for 104.36.160.0/23 with origin AS20333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20333 in the RIR database for the space.673 of 673
ROA: none206.198.136.0/24No ROA covers it. Add a ROA for AS20333, maxLength 24.673 of 673
Route object: none206.198.136.0/24No route object for it. A route object for 206.198.136.0/21 with origin AS20333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20333 in the RIR database for the space.673 of 673
ROA: none206.198.137.0/24No ROA covers it. Add a ROA for AS20333, maxLength 24.673 of 673
Route object: none206.198.137.0/24No route object for it. A route object for 206.198.136.0/21 with origin AS20333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20333 in the RIR database for the space.673 of 673
ROA: none206.198.138.0/24No ROA covers it. Add a ROA for AS20333, maxLength 24.673 of 673
Route object: none206.198.138.0/24No route object for it. A route object for 206.198.136.0/21 with origin AS20333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20333 in the RIR database for the space.673 of 673
ROA: none206.198.139.0/24No ROA covers it. Add a ROA for AS20333, maxLength 24.673 of 673
Route object: none206.198.139.0/24No route object for it. A route object for 206.198.136.0/21 with origin AS20333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20333 in the RIR database for the space.673 of 673
ROA: none199.89.51.0/24No ROA covers it. Add a ROA for AS20333, maxLength 24.673 of 673
Route object: RIR199.89.51.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none207.67.99.0/24No ROA covers it. Add a ROA for AS20333, maxLength 24.673 of 673
Route object: RIR207.67.99.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

104.36.160.0/23ALTDB, RADBNo ROA
199.89.50.0/23ALTDB, RADBNo ROA
199.89.50.0/24ALTDBNo ROA
206.198.136.0/21ALTDB, RADBNo ROA

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.