bgpreport

Network · data from 2026-11-12

AS21660 BAXALTA - Baxalta Incorporated

Registry name: BAXALTA - Baxalta Incorporated, US · not in PeeringDB

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

Announced routes

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

63.84.72.0/23 No ROA None 673 100% 67
63.84.74.0/24 No ROA None 673 100% 67
63.84.75.0/24 No ROA None 673 100% 67
104.254.253.0/24 No ROA None 673 100% 67
63.244.0.0/22 No ROA Other IRR onlyRADB 673 100% 67
43.229.156.0/23 No ROA Other IRR onlyRADB 672 100% 67
43.229.158.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.48.172.0/24 No ROA Other IRR onlyRADB 672 100% 67
185.89.148.0/23 Valid RIR databaseRIPE 672 100% 67
185.89.150.0/24 Valid RIR databaseRIPE 672 100% 67
185.89.151.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS21660 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 21 are in fix.csv.

  • ROA: none8
  • Route object: none4
  • Route object: RIR4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none63.84.72.0/23No ROA covers it. Add a ROA for AS21660, maxLength 23.673 of 673
Route object: none63.84.72.0/23No route object for it. Add a route object with origin AS21660 in the RIR database for the space.673 of 673
ROA: none63.84.74.0/24No ROA covers it. Add a ROA for AS21660, maxLength 24.673 of 673
Route object: none63.84.74.0/24No route object for it. Add a route object with origin AS21660 in the RIR database for the space.673 of 673
ROA: none63.84.75.0/24No ROA covers it. Add a ROA for AS21660, maxLength 24.673 of 673
Route object: none63.84.75.0/24No route object for it. Add a route object with origin AS21660 in the RIR database for the space.673 of 673
ROA: none104.254.253.0/24No ROA covers it. Add a ROA for AS21660, maxLength 24.673 of 673
Route object: none104.254.253.0/24No route object for it. Add a route object with origin AS21660 in the RIR database for the space.673 of 673
ROA: none63.244.0.0/22No ROA covers it. Add a ROA for AS21660, maxLength 22.673 of 673
Route object: RIR63.244.0.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none43.229.156.0/23No ROA covers it. Add a ROA for AS21660, maxLength 23.672 of 673
Route object: RIR43.229.156.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none43.229.158.0/24No ROA covers it. Add a ROA for AS21660, maxLength 24.672 of 673
Route object: RIR43.229.158.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.48.172.0/24No ROA covers it. Add a ROA for AS21660, maxLength 24.672 of 673
Route object: RIR103.48.172.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

43.229.156.0/22NTTCOMNo ROA
64.201.191.0/24BELLNo ROA
103.48.172.0/22NTTCOMNo ROA
185.89.148.0/22RIPENo ROA
2a03:82a0::/32RIPENo 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.