bgpreport

Network · data from 2026-11-12

AS7152 REDCROSS-ASN - American Red Cross

Registry name: REDCROSS-ASN - American Red Cross, US · not in PeeringDB

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

Announced routes

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

162.6.0.0/16 No ROA Other IRR onlyRADB 673 100% 67
162.6.0.0/21 No ROA Other IRR onlyRADB 673 100% 67
162.6.40.0/23 No ROA Other IRR onlyRADB 673 100% 67
162.6.48.0/21 No ROA Other IRR onlyRADB 673 100% 67
162.6.52.0/22 No ROA Other IRR onlyRADB 673 100% 67
162.6.96.0/20 No ROA Other IRR onlyRADB 673 100% 67
162.6.97.0/24 No ROA Other IRR onlyRADB 673 100% 67
162.6.99.0/24 No ROA Other IRR onlyRADB 673 100% 67
162.6.100.0/24 No ROA Other IRR onlyRADB 673 100% 67
162.6.101.0/24 No ROA Other IRR onlyRADB 673 100% 67
162.6.112.0/20 No ROA Other IRR onlyRADB 673 100% 67
162.6.192.0/20 No ROA Other IRR onlyRADB 673 100% 67
162.6.215.0/24 No ROA Other IRR onlyRADB 673 100% 67
162.6.216.0/23 No ROA Other IRR onlyRADB 673 100% 67
162.6.220.0/22 No ROA Other IRR onlyRADB 673 100% 67
162.6.224.0/19 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS7152 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 32 are in fix.csv.

  • ROA: none16
  • Route object: RIR16
ChangePrefix or setDetailFull-table peers
ROA: none162.6.0.0/16No ROA covers it. Add a ROA for AS7152, maxLength 16.673 of 673
Route object: RIR162.6.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.0.0/21No ROA covers it. Add a ROA for AS7152, maxLength 21.673 of 673
Route object: RIR162.6.0.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.40.0/23No ROA covers it. Add a ROA for AS7152, maxLength 23.673 of 673
Route object: RIR162.6.40.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.48.0/21No ROA covers it. Add a ROA for AS7152, maxLength 21.673 of 673
Route object: RIR162.6.48.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.52.0/22No ROA covers it. Add a ROA for AS7152, maxLength 22.673 of 673
Route object: RIR162.6.52.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.96.0/20No ROA covers it. Add a ROA for AS7152, maxLength 20.673 of 673
Route object: RIR162.6.96.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.97.0/24No ROA covers it. Add a ROA for AS7152, maxLength 24.673 of 673
Route object: RIR162.6.97.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.99.0/24No ROA covers it. Add a ROA for AS7152, maxLength 24.673 of 673
Route object: RIR162.6.99.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.100.0/24No ROA covers it. Add a ROA for AS7152, maxLength 24.673 of 673
Route object: RIR162.6.100.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.101.0/24No ROA covers it. Add a ROA for AS7152, maxLength 24.673 of 673
Route object: RIR162.6.101.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.112.0/20No ROA covers it. Add a ROA for AS7152, maxLength 20.673 of 673
Route object: RIR162.6.112.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.192.0/20No ROA covers it. Add a ROA for AS7152, maxLength 20.673 of 673
Route object: RIR162.6.192.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.215.0/24No ROA covers it. Add a ROA for AS7152, maxLength 24.673 of 673
Route object: RIR162.6.215.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.216.0/23No ROA covers it. Add a ROA for AS7152, maxLength 23.673 of 673
Route object: RIR162.6.216.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.220.0/22No ROA covers it. Add a ROA for AS7152, maxLength 22.673 of 673
Route object: RIR162.6.220.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.6.224.0/19No ROA covers it. Add a ROA for AS7152, maxLength 19.673 of 673
Route object: RIR162.6.224.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS7152 is announced.

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.