bgpreport

Network · data from 2026-11-12

AS14639 CARDINALHEALTH-AS02 - Cardinal Health, Inc.

Registry name: CARDINALHEALTH-AS02 - Cardinal Health, Inc., US · not in PeeringDB

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

Announced routes

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

12.20.127.0/24 No ROA None 673 100% 67
199.230.151.0/24 Valid Nonecovered by 199.230.128.0/17 673 100% 67
199.230.154.0/24 Valid Nonecovered by 199.230.128.0/17 673 100% 67
199.230.155.0/24 Valid Nonecovered by 199.230.128.0/17 673 100% 67
199.230.170.0/23 Valid Nonecovered by 199.230.128.0/17 673 100% 67
199.230.172.0/24 Valid Nonecovered by 199.230.128.0/17 673 100% 67
199.230.200.0/23 Valid Nonecovered by 199.230.128.0/17 673 100% 67
199.230.203.0/24 Valid Nonecovered by 199.230.128.0/17 673 100% 67
199.230.209.0/24 Valid Nonecovered by 199.230.128.0/17 673 100% 67
199.230.212.0/23 Valid Nonecovered by 199.230.128.0/17 673 100% 67
199.230.230.0/24 Valid Nonecovered by 199.230.128.0/17 673 100% 67
2602:fd26::/48 Valid Nonecovered by 2602:fd26::/36 636 100% 67

AS-SET

AS14639 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 19 are in fix.csv.

  • ROA: none1
  • Route object: none12
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none12.20.127.0/24No ROA covers it. Add a ROA for AS14639, maxLength 24.673 of 673
Route object: none12.20.127.0/24No route object for it. Add a route object with origin AS14639 in the RIR database for the space.673 of 673
Route object: none199.230.151.0/24No route object for it. A route object for 199.230.128.0/17 with origin AS14639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14639 in the RIR database for the space.673 of 673
Route object: none199.230.154.0/24No route object for it. A route object for 199.230.128.0/17 with origin AS14639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14639 in the RIR database for the space.673 of 673
Route object: none199.230.155.0/24No route object for it. A route object for 199.230.128.0/17 with origin AS14639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14639 in the RIR database for the space.673 of 673
Route object: none199.230.170.0/23No route object for it. A route object for 199.230.128.0/17 with origin AS14639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14639 in the RIR database for the space.673 of 673
Route object: none199.230.172.0/24No route object for it. A route object for 199.230.128.0/17 with origin AS14639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14639 in the RIR database for the space.673 of 673
Route object: none199.230.200.0/23No route object for it. A route object for 199.230.128.0/17 with origin AS14639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14639 in the RIR database for the space.673 of 673
Route object: none199.230.203.0/24No route object for it. A route object for 199.230.128.0/17 with origin AS14639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14639 in the RIR database for the space.673 of 673
Route object: none199.230.209.0/24No route object for it. A route object for 199.230.128.0/17 with origin AS14639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14639 in the RIR database for the space.673 of 673
Route object: none199.230.212.0/23No route object for it. A route object for 199.230.128.0/17 with origin AS14639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14639 in the RIR database for the space.673 of 673
Route object: none199.230.230.0/24No route object for it. A route object for 199.230.128.0/17 with origin AS14639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14639 in the RIR database for the space.673 of 673
Route object: none2602:fd26::/48No route object for it. A route object for 2602:fd26::/36 with origin AS14639 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14639 in the RIR database for the space.636 of 636

Route objects not announced

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

143.98.0.0/16ARINValid
198.89.160.0/20ARINValid
198.89.176.0/21ARINValid
198.89.184.0/23ARINValid
199.230.128.0/17ARINValid
2602:fd26::/36ARINValid

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.