subnet.im

AS395174Iron Mountain Data Center

United StatesRegistryARIN

As of 27th September 2026, AS395174 (Iron Mountain Data Center), a network registered in the United States with ARIN, originates 3 IPv4 prefixes covering 1k addresses and 9 IPv6 prefixes. By IPv4 address space that makes it the 35,810th-largest of the 79,516 networks we see originating IPv4, and the 8,138th-largest of 18,424 in the United States. It is seen behind 3 upstream networks, most often AS3356 (Lumen (Level 3)) and AS3491 (PCCW Global (HK) Ltd.), and in front of 2 downstream networks. 25% of its announcements have a valid RPKI ROA, and none are RPKI-invalid. 100% of its routes reach at least 90% of full-feed peers.

At a glance

IPv4 prefixes

3

IPv6 prefixes

9

IPv4 addresses

1k

IPv6 /64s

286M

Upstream graph

The networks AS395174 is seen behind, one and two hops out, drawn from real AS paths.

AS395174Toward the internet core
Upstream graph for AS395174: 9 neighbouring networks observed beyond it across 2 levels. The same networks are listed in the tables below.AS395174Iron Mountain Dat…This networkAS1299Arelion (fka. Tel…AS3356Lumen (Level 3)AS3491PCCW Global (HK) …AS8888xTom Pty LtdAS13030Init7 (Switzerlan…AS2914NTT America, Inc.AS3549Lumen (fka. Globa…AS24516Virtutel Pty LtdAS58511Swoop (Anycast Gl…

Networks observed one and two hops upstream of AS395174 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.

Neighbouring networks

10

adjacent networks

Upstreams
330%
Peers
550%
Downstreams
220%

Networks carrying this one's traffic toward the rest of the internet.

Upstreams of AS395174
NetworkCountryRelationshipPathsVantage pts
AS3356Lumen (Level 3)USPeer50787
AS3491PCCW Global (HK) Ltd.HKPeer29950
AS1299Arelion (fka. Telia Carrier)SEPeer25555

Prefixes

The largest blocks AS395174 originates, widest first.

Largest prefixes originated by AS395174
PrefixAddressesVisibility
148.51.222.0/2351281/81
148.51.239.0/2425681/81
148.51.240.0/2425681/81
2605:3380:d000::/36268M × /6464/64
2605:3380:4d00::/4016.8M × /6464/64
2605:3380:4d01::/4865.5k × /6464/64
2605:3380:4d02::/4865.5k × /6464/64
2605:3380:4d03::/4865.5k × /6464/64
2605:3380:4d04::/4865.5k × /6464/64
2605:3380:4d06::/4865.5k × /6464/64

Routing health

How AS395174's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.

RPKI origin validation

  • Valid25.0%3
  • Invalid0.0%0
  • No ROA75.0%9

Propagation

  • Globally propagated90% of full-feed peers or more100.0%12
  • Partially propagated40% to 90%0.0%0
  • Seen by few peersUnder 40%0.0%0

Prefix sizes

IPv4 — 3 prefixes

IPv6 — 9 prefixes

  • /36268M × /6411.1%1
  • /4016.8M × /6411.1%1
  • /4865.5k × /6477.8%7

Recent changes

Announcements that started or stopped since 28th Aug 2026.

No announcement by AS395174 started or stopped in this period.

Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.