bgpreport

Network · data from 2026-11-12

AS10599 MCKESSON - McKesson Corp.

Registry name: MCKESSON - McKesson Corp., US · not in PeeringDB

15IPv4 routes 40.0% RPKI valid · 73.3% with a route object
0IPv6 routes
1RPKI invalid 0 origin · 1 maxLength
8No ROA 4 with no route object for this origin
9Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS10599, seen from no peer

Announced routes

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

143.112.76.0/24 Invalid: maxLength RIR databaseARIN 2 0%low visibility 2
139.177.127.0/24 No ROA None 5 1%low visibility 4
149.21.0.0/16 No ROA None 2 0%low visibility 3
206.203.64.0/18 No ROA Other origin only 2 0%low visibility 3
194.61.251.0/24 No ROA RIR databaseRIPE 672 100% 66
206.203.65.0/24 No ROA RIR databaseARIN 672 100% 67
206.203.73.0/24 No ROA RIR databaseARIN 672 100% 66
206.203.74.0/24 No ROA RIR databaseARIN 672 100% 67
206.203.67.0/24 No ROA RIR databaseARIN 208 31% 50
143.112.128.0/22 Valid Nonecovered by 143.112.128.0/18 3 0%low visibility 1
206.203.78.0/24 Valid RIR databaseARIN 107 16% 38
143.112.128.0/18 Valid RIR databaseARIN 5 1%low visibility 4
143.112.192.0/19 Valid RIR databaseARIN 5 1%low visibility 4
143.112.0.0/17 Valid RIR databaseARIN 1 0%low visibility 2
143.112.224.0/19 Valid RIR databaseARIN 1 0%low visibility 2

AS-SET

AS10599 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 14 are in fix.csv.

  • ROA: maxLength1
  • ROA: none8
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength143.112.76.0/24ROA 143.112.0.0/17 AS10599 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 143.112.76.0/24.2 of 673
ROA: none139.177.127.0/24No ROA covers it. Add a ROA for AS10599, maxLength 24.5 of 673
Route object: none139.177.127.0/24No route object for it. Add a route object with origin AS10599 in the RIR database for the space.5 of 673
ROA: none149.21.0.0/16No ROA covers it. Add a ROA for AS10599, maxLength 16.2 of 673
Route object: none149.21.0.0/16No route object for it. Add a route object with origin AS10599 in the RIR database for the space.2 of 673
ROA: none206.203.64.0/18No ROA covers it. Add a ROA for AS10599, maxLength 18.2 of 673
Route object: none206.203.64.0/18Route objects for it name AS19842. Add a route object with origin AS10599 in the RIR database for the space.2 of 673
ROA: none194.61.251.0/24No ROA covers it. Add a ROA for AS10599, maxLength 24.672 of 673
ROA: none206.203.65.0/24No ROA covers it. Add a ROA for AS10599, maxLength 24.672 of 673
ROA: none206.203.73.0/24No ROA covers it. Add a ROA for AS10599, maxLength 24.672 of 673
ROA: none206.203.74.0/24No ROA covers it. Add a ROA for AS10599, maxLength 24.672 of 673
ROA: none206.203.67.0/24No ROA covers it. Add a ROA for AS10599, maxLength 24.208 of 673
Route object: none143.112.128.0/22No route object for it. A route object for 143.112.128.0/18 with origin AS10599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10599 in the RIR database for the space.3 of 673

Route objects not announced

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

143.112.198.0/24ARINValid

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.