bgpreport

Network · data from 2026-11-12

AS21549 IRON-MOUNTAIN - Iron Mountain Inc

Registry name: IRON-MOUNTAIN - Iron Mountain Inc, US · not in PeeringDB

17IPv4 routes 23.5% RPKI valid · 64.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
13No ROA 6 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
17Route objects not announced registered with origin AS21549, seen from no peer

Announced routes

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

170.62.126.0/24 No ROA Nonecovered by 170.62.126.0/23 672 100% 67
208.66.142.0/23 No ROA Nonecovered by 208.66.136.0/21 672 100% 67
216.229.152.0/23 No ROA Nonecovered by 216.229.144.0/20 672 100% 67
216.229.156.0/22 No ROA Nonecovered by 216.229.144.0/20 672 100% 67
113.29.109.0/26 No ROA None 2 0%low visibility 2
113.29.110.192/26 No ROA None 2 0%low visibility 2
170.62.38.0/24 No ROA Other IRR onlyRADB 672 100% 67
208.66.139.0/24 No ROA Other IRR onlyRADB 672 100% 67
216.229.144.0/24 No ROA Other IRR onlyRADB 672 100% 67
216.229.145.0/24 No ROA Other IRR onlyRADB 672 100% 67
216.229.146.0/24 No ROA Other IRR onlyRADB 672 100% 67
216.229.147.0/24 No ROA Other IRR onlyRADB 672 100% 67
216.229.154.0/24 No ROA Other IRR onlyRADB 672 100% 67
138.207.75.0/24 Valid RIR databaseARIN 673 100% 67
138.207.76.0/24 Valid RIR databaseARIN 673 100% 67
138.207.77.0/24 Valid RIR databaseARIN 673 100% 67
138.207.79.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

AS21549 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 43 are in fix.csv.

  • ROA: none13
  • Route object: none6
  • Route object: RIR7
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none170.62.126.0/24No ROA covers it. Add a ROA for AS21549, maxLength 24.672 of 673
Route object: none170.62.126.0/24No route object for it. A route object for 170.62.126.0/23 with origin AS21549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21549 in the RIR database for the space.672 of 673
ROA: none208.66.142.0/23No ROA covers it. Add a ROA for AS21549, maxLength 23.672 of 673
Route object: none208.66.142.0/23No route object for it. A route object for 208.66.136.0/21 with origin AS21549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21549 in the RIR database for the space.672 of 673
ROA: none216.229.152.0/23No ROA covers it. Add a ROA for AS21549, maxLength 23.672 of 673
Route object: none216.229.152.0/23No route object for it. A route object for 216.229.144.0/20 with origin AS21549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21549 in the RIR database for the space.672 of 673
ROA: none216.229.156.0/22No ROA covers it. Add a ROA for AS21549, maxLength 22.672 of 673
Route object: none216.229.156.0/22No route object for it. A route object for 216.229.144.0/20 with origin AS21549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21549 in the RIR database for the space.672 of 673
ROA: none113.29.109.0/26No ROA covers it. Add a ROA for AS21549, maxLength 26.2 of 673
Route object: none113.29.109.0/26No route object for it. Add a route object with origin AS21549 in the RIR database for the space.2 of 673
ROA: none113.29.110.192/26No ROA covers it. Add a ROA for AS21549, maxLength 26.2 of 673
Route object: none113.29.110.192/26No route object for it. Add a route object with origin AS21549 in the RIR database for the space.2 of 673
ROA: none170.62.38.0/24No ROA covers it. Add a ROA for AS21549, maxLength 24.672 of 673
Route object: RIR170.62.38.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none208.66.139.0/24No ROA covers it. Add a ROA for AS21549, maxLength 24.672 of 673
Route object: RIR208.66.139.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none216.229.144.0/24No ROA covers it. Add a ROA for AS21549, maxLength 24.672 of 673
Route object: RIR216.229.144.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none216.229.145.0/24No ROA covers it. Add a ROA for AS21549, maxLength 24.672 of 673
Route object: RIR216.229.145.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none216.229.146.0/24No ROA covers it. Add a ROA for AS21549, maxLength 24.672 of 673
Route object: RIR216.229.146.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none216.229.147.0/24No ROA covers it. Add a ROA for AS21549, maxLength 24.672 of 673
Route object: RIR216.229.147.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none216.229.154.0/24No ROA covers it. Add a ROA for AS21549, maxLength 24.672 of 673
Route object: RIR216.229.154.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 AS21549 whose prefix no peer sees AS21549 announce. Many are kept on purpose (backup routes, space announced only in some places).

63.251.140.0/24RADBNo ROA
64.95.74.0/23RADBNo ROA
64.95.75.0/24RADBNo ROA
170.62.126.0/23RADBNo ROA
208.66.136.0/21RADBNo ROA
208.66.138.0/24RADBNo ROA
208.66.142.0/24RADBNo ROA
208.66.143.0/24RADBNo ROA
216.229.144.0/20RADBNo ROA
216.229.149.0/24RADBNo ROA
216.229.150.0/24RADBNo ROA
216.229.152.0/24RADBNo ROA
216.229.153.0/24RADBNo ROA
216.229.156.0/24RADBNo ROA
216.229.157.0/24RADBNo ROA
216.229.158.0/24RADBNo ROA
216.229.159.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.