bgpreport

Network · data from 2026-11-12

AS14822 MSKCC - Memorial Sloan-Kettering Cancer Center

Registry name: MSKCC - Memorial Sloan-Kettering Cancer Center, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14822, 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.
140.163.0.0/16 No ROA Other IRR onlyRADB 672 100% 67
140.163.0.0/17 No ROA Other IRR onlyRADB 672 100% 67
140.163.64.0/24 No ROA Other IRR onlyRADB 672 100% 67
140.163.70.0/24 No ROA Other IRR onlyRADB 672 100% 67
140.163.128.0/17 No ROA Other IRR onlyRADB 672 100% 67
192.55.249.0/24 No ROA Other IRR onlyRADB 672 100% 67
47.19.120.0/24 Valid RIR databaseARIN, RADB 672 100% 67

AS-SET

AS14822 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: none6
  • Route object: RIR6
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none140.163.0.0/16No ROA covers it. Add a ROA for AS14822, maxLength 16.672 of 673
Route object: RIR140.163.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none140.163.0.0/17No ROA covers it. Add a ROA for AS14822, maxLength 17.672 of 673
Route object: RIR140.163.0.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none140.163.64.0/24No ROA covers it. Add a ROA for AS14822, maxLength 24.672 of 673
Route object: RIR140.163.64.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none140.163.70.0/24No ROA covers it. Add a ROA for AS14822, maxLength 24.672 of 673
Route object: RIR140.163.70.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none140.163.128.0/17No ROA covers it. Add a ROA for AS14822, maxLength 17.672 of 673
Route object: RIR140.163.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none192.55.249.0/24No ROA covers it. Add a ROA for AS14822, maxLength 24.672 of 673
Route object: RIR192.55.249.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 AS14822 whose prefix no peer sees AS14822 announce. Many are kept on purpose (backup routes, space announced only in some places).

40.129.160.0/24RADBValid
140.163.0.0/24RADBNo ROA
140.163.1.0/24RADBNo ROA
140.163.4.0/24RADBNo ROA
140.163.6.0/24RADBNo ROA
140.163.53.0/24RADBNo ROA
140.163.222.0/24RADBNo ROA
140.163.223.0/24RADBNo ROA
140.163.254.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.