Network · data from 2026-11-12
AS22855 CARDINALHEALTH-AS01 - Cardinal Health, Inc.
Registry name: CARDINALHEALTH-AS01 - Cardinal Health, Inc., US · not in PeeringDB
17IPv4 routes
100.0% 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
0No ROA
18 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
6Route objects not announced
registered with origin AS22855, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS22855, 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.
| 198.89.160.0/24 | Valid | Nonecovered by 198.89.160.0/20 | 673 100% |
| 198.89.166.0/24 | Valid | Nonecovered by 198.89.160.0/20 | 673 100% |
| 198.89.167.0/24 | Valid | Nonecovered by 198.89.160.0/20 | 673 100% |
| 198.89.170.0/23 | Valid | Nonecovered by 198.89.160.0/20 | 673 100% |
| 199.230.128.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 199.230.129.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 199.230.136.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 199.230.138.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 199.230.139.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 199.230.150.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 199.230.164.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 199.230.231.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 199.230.249.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 199.230.252.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 199.230.253.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 199.230.254.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 199.230.255.0/24 | Valid | Nonecovered by 199.230.128.0/17 | 673 100% |
| 2602:fd26:1::/48 | Valid | Nonecovered by 2602:fd26::/36 | 636 100% |
AS-SET
AS22855 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 24 are in fix.csv.
- Route object: none18
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 198.89.160.0/24 | No route object for it. A route object for 198.89.160.0/20 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 198.89.166.0/24 | No route object for it. A route object for 198.89.160.0/20 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 198.89.167.0/24 | No route object for it. A route object for 198.89.160.0/20 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 198.89.170.0/23 | No route object for it. A route object for 198.89.160.0/20 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.128.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.129.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.136.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.138.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.139.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.150.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.164.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.231.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.249.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.252.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.253.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.254.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 199.230.255.0/24 | No route object for it. A route object for 199.230.128.0/17 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
| Route object: none | 2602:fd26:1::/48 | No route object for it. A route object for 2602:fd26::/36 with origin AS22855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22855 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS22855 whose prefix no peer sees AS22855 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 143.98.0.0/16 | ARIN | Valid |
| 198.89.160.0/20 | ARIN | Valid |
| 198.89.176.0/21 | ARIN | Valid |
| 198.89.184.0/23 | ARIN | Valid |
| 199.230.128.0/17 | ARIN | Valid |
| 2602:fd26::/36 | ARIN | Valid |
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.