bgpreport

Network · data from 2026-11-12

AS11951 MCSP - Medical Computer Systems

Registry name: MCSP - Medical Computer Systems, US · not in PeeringDB

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

Announced routes

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

66.186.129.0/24 No ROA Nonecovered by 66.186.128.0/20 672 100% 67
204.152.42.0/24 No ROA Nonecovered by 204.152.42.0/23 672 100% 67
207.152.134.0/24 No ROA Nonecovered by 207.152.128.0/18 672 100% 67
207.152.135.0/24 No ROA Nonecovered by 207.152.128.0/18 672 100% 67
209.50.193.0/24 No ROA Nonecovered by 209.50.192.0/19 672 100% 67
204.152.43.0/24 No ROA Nonecovered by 204.152.42.0/23 2 0%low visibility 2
66.186.128.0/20 No ROA Other IRR onlyRADB 672 100% 67
204.152.42.0/23 No ROA Other IRR onlyRADB 672 100% 67
205.147.160.0/19 No ROA Other IRR onlyRADB 672 100% 67
207.152.128.0/18 No ROA Other IRR onlyRADB 672 100% 67
209.50.192.0/19 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS11951 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 29 are in fix.csv.

  • ROA: none11
  • Route object: none6
  • Route object: RIR5
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none66.186.129.0/24No ROA covers it. Add a ROA for AS11951, maxLength 24.672 of 673
Route object: none66.186.129.0/24No route object for it. A route object for 66.186.128.0/20 with origin AS11951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11951 in the RIR database for the space.672 of 673
ROA: none204.152.42.0/24No ROA covers it. Add a ROA for AS11951, maxLength 24.672 of 673
Route object: none204.152.42.0/24No route object for it. A route object for 204.152.42.0/23 with origin AS11951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11951 in the RIR database for the space.672 of 673
ROA: none207.152.134.0/24No ROA covers it. Add a ROA for AS11951, maxLength 24.672 of 673
Route object: none207.152.134.0/24No route object for it. A route object for 207.152.128.0/18 with origin AS11951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11951 in the RIR database for the space.672 of 673
ROA: none207.152.135.0/24No ROA covers it. Add a ROA for AS11951, maxLength 24.672 of 673
Route object: none207.152.135.0/24No route object for it. A route object for 207.152.128.0/18 with origin AS11951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11951 in the RIR database for the space.672 of 673
ROA: none209.50.193.0/24No ROA covers it. Add a ROA for AS11951, maxLength 24.672 of 673
Route object: none209.50.193.0/24No route object for it. A route object for 209.50.192.0/19 with origin AS11951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11951 in the RIR database for the space.672 of 673
ROA: none204.152.43.0/24No ROA covers it. Add a ROA for AS11951, maxLength 24.2 of 673
Route object: none204.152.43.0/24No route object for it. A route object for 204.152.42.0/23 with origin AS11951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11951 in the RIR database for the space.2 of 673
ROA: none66.186.128.0/20No ROA covers it. Add a ROA for AS11951, maxLength 20.672 of 673
Route object: RIR66.186.128.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none204.152.42.0/23No ROA covers it. Add a ROA for AS11951, maxLength 23.672 of 673
Route object: RIR204.152.42.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none205.147.160.0/19No ROA covers it. Add a ROA for AS11951, maxLength 19.672 of 673
Route object: RIR205.147.160.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none207.152.128.0/18No ROA covers it. Add a ROA for AS11951, maxLength 18.672 of 673
Route object: RIR207.152.128.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none209.50.192.0/19No ROA covers it. Add a ROA for AS11951, maxLength 19.672 of 673
Route object: RIR209.50.192.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

199.5.133.0/24RADBNo ROA
207.152.133.0/24RADBNo ROA
207.152.183.0/24RADBNo ROA
207.152.188.0/24RADBNo ROA
209.50.213.0/24ALTDBNo ROA
209.50.214.0/24RADBNo ROA
209.50.218.0/24RADBNo 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.