bgpreport

Network · data from 2026-11-12

AS46552 RSMUS-IAAS - RSM

Registry name: RSMUS-IAAS - RSM, US · not in PeeringDB

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

Announced routes

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

173.240.64.0/22 No ROA Other origin onlycovered by 173.240.64.0/20 673 100% 67
173.240.72.0/23 No ROA Nonecovered by 173.240.72.0/21 673 100% 67
173.240.74.0/23 No ROA Nonecovered by 173.240.72.0/21 673 100% 67
173.240.76.0/23 No ROA Nonecovered by 173.240.72.0/21 673 100% 67
173.240.78.0/23 No ROA Nonecovered by 173.240.72.0/21 673 100% 67
173.240.64.0/23 No ROA Other origin onlycovered by 173.240.64.0/20 671 100% 68
173.240.70.0/23 No ROA Nonecovered by 173.240.64.0/20 671 100% 68
173.240.71.0/24 No ROA Other origin onlycovered by 173.240.64.0/20 671 100% 68
173.240.76.0/22 No ROA Nonecovered by 173.240.72.0/21 671 100% 68
208.88.236.0/23 No ROA Other IRR onlyRADB 671 100% 68
208.88.238.0/23 No ROA Other IRR onlyRADB 671 100% 68
208.88.236.0/22 No ROA RIR databaseARIN, RADB 671 100% 68

AS-SET

AS46552 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 29 are in fix.csv.

  • ROA: none12
  • Route object: none9
  • Route object: RIR2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none173.240.64.0/22No ROA covers it. Add a ROA for AS46552, maxLength 22.673 of 673
Route object: none173.240.64.0/22Route objects for it name AS198949, AS393238. A route object for 173.240.64.0/20 with origin AS46552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46552 in the RIR database for the space.673 of 673
ROA: none173.240.72.0/23No ROA covers it. Add a ROA for AS46552, maxLength 23.673 of 673
Route object: none173.240.72.0/23No route object for it. A route object for 173.240.72.0/21 with origin AS46552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46552 in the RIR database for the space.673 of 673
ROA: none173.240.74.0/23No ROA covers it. Add a ROA for AS46552, maxLength 23.673 of 673
Route object: none173.240.74.0/23No route object for it. A route object for 173.240.72.0/21 with origin AS46552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46552 in the RIR database for the space.673 of 673
ROA: none173.240.76.0/23No ROA covers it. Add a ROA for AS46552, maxLength 23.673 of 673
Route object: none173.240.76.0/23No route object for it. A route object for 173.240.72.0/21 with origin AS46552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46552 in the RIR database for the space.673 of 673
ROA: none173.240.78.0/23No ROA covers it. Add a ROA for AS46552, maxLength 23.673 of 673
Route object: none173.240.78.0/23No route object for it. A route object for 173.240.72.0/21 with origin AS46552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46552 in the RIR database for the space.673 of 673
ROA: none173.240.64.0/23No ROA covers it. Add a ROA for AS46552, maxLength 23.671 of 673
Route object: none173.240.64.0/23Route objects for it name AS393238. A route object for 173.240.64.0/20 with origin AS46552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46552 in the RIR database for the space.671 of 673
ROA: none173.240.70.0/23No ROA covers it. Add a ROA for AS46552, maxLength 23.671 of 673
Route object: none173.240.70.0/23No route object for it. A route object for 173.240.64.0/20 with origin AS46552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46552 in the RIR database for the space.671 of 673
ROA: none173.240.71.0/24No ROA covers it. Add a ROA for AS46552, maxLength 24.671 of 673
Route object: none173.240.71.0/24Route objects for it name AS14230. A route object for 173.240.64.0/20 with origin AS46552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46552 in the RIR database for the space.671 of 673
ROA: none173.240.76.0/22No ROA covers it. Add a ROA for AS46552, maxLength 22.671 of 673
Route object: none173.240.76.0/22No route object for it. A route object for 173.240.72.0/21 with origin AS46552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46552 in the RIR database for the space.671 of 673
ROA: none208.88.236.0/23No ROA covers it. Add a ROA for AS46552, maxLength 23.671 of 673
Route object: RIR208.88.236.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none208.88.238.0/23No ROA covers it. Add a ROA for AS46552, maxLength 23.671 of 673
Route object: RIR208.88.238.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none208.88.236.0/22No ROA covers it. Add a ROA for AS46552, maxLength 22.671 of 673

Route objects not announced

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

173.240.64.0/20RADBNo ROA
173.240.72.0/21RADBNo ROA
208.88.236.0/24RADBNo ROA
208.88.237.0/24RADBNo ROA
208.88.238.0/24RADBNo ROA
208.88.239.0/24RADBNo 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.