bgpreport

Network · data from 2026-11-12

AS11452 MOUNT-SINAI - Mount Sinai School of Medicine

Registry name: MOUNT-SINAI - Mount Sinai School of Medicine, US · not in PeeringDB

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

Announced routes

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

146.203.128.0/21 No ROA None 672 100% 68
146.203.192.0/18 No ROA Other origin only 672 100% 68
159.123.127.0/24 No ROA None 672 100% 67
146.203.0.0/18 No ROA Other origin only 670 100% 68
146.203.64.0/18 No ROA Other origin only 670 100% 68
146.203.138.0/24 Valid Other IRR onlyRADB 671 100% 67
146.203.139.0/24 Valid Other IRR onlyRADB 671 100% 67
146.203.148.0/24 Valid Other IRR onlyRADB 671 100% 67
146.203.149.0/24 Valid Other IRR onlyRADB 671 100% 67
146.203.150.0/24 Valid Other IRR onlyRADB 671 100% 67
146.203.151.0/24 Valid Other IRR onlyRADB 671 100% 67
146.203.136.0/21 Valid RIR databaseARIN 672 100% 67
146.203.144.0/22 Valid RIR databaseARIN 672 100% 67
146.203.148.0/22 Valid RIR databaseARIN 672 100% 67

AS-SET

AS11452 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 17 are in fix.csv.

  • ROA: none5
  • Route object: none5
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none146.203.128.0/21No ROA covers it. Add a ROA for AS11452, maxLength 21.672 of 673
Route object: none146.203.128.0/21No route object for it. Add a route object with origin AS11452 in the RIR database for the space.672 of 673
ROA: none146.203.192.0/18No ROA covers it. Add a ROA for AS11452, maxLength 18.672 of 673
Route object: none146.203.192.0/18Route objects for it name AS7029. Add a route object with origin AS11452 in the RIR database for the space.672 of 673
ROA: none159.123.127.0/24No ROA covers it. Add a ROA for AS11452, maxLength 24.672 of 673
Route object: none159.123.127.0/24No route object for it. Add a route object with origin AS11452 in the RIR database for the space.672 of 673
ROA: none146.203.0.0/18No ROA covers it. Add a ROA for AS11452, maxLength 18.670 of 673
Route object: none146.203.0.0/18Route objects for it name AS7029. Add a route object with origin AS11452 in the RIR database for the space.670 of 673
ROA: none146.203.64.0/18No ROA covers it. Add a ROA for AS11452, maxLength 18.670 of 673
Route object: none146.203.64.0/18Route objects for it name AS7029. Add a route object with origin AS11452 in the RIR database for the space.670 of 673
Route object: RIR146.203.138.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR146.203.139.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR146.203.148.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR146.203.149.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR146.203.150.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR146.203.151.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

146.203.135.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.