Autonomous system
AS12025 IMDC-AS12025 - Iron Mountain Data Center
Unclassified ARIN NSP
Summary
Iron Mountain Data Center
hosting colo datacenter legacy
The colocation network of Iron Mountain, the records-storage company that moved into wholesale and retail data centres.
What it's used for
- Colocation and interconnection for enterprise tenants, with the address space handed out to customers inside the facilities.
Notable
- 98 observed BGP neighbours against 122,000 addresses, spread over 137 IPv4 prefixes and 583 IPv6 prefixes. Heavy fragmentation plus a high neighbour count is what a carrier- neutral colocation floor looks like: lots of separate customer assignments and lots of networks to interconnect with.
- Every RDAP record resolves back to Iron Mountain Data Center under
IMDC-netnames, so unlike many colocation operators this one holds its space directly rather than announcing a patchwork of tenant-registered blocks.
Interesting
- A sampled address still answers under
iodatacenters.com. IO Data Centers was the Phoenix-based operator Iron Mountain bought in 2017, and several netnames carry anAZPsuffix that lines up with that Arizona origin. The acquisition is visible in the naming years after the brand disappeared.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| DE-CIX New York | New York, United States | 206.82.105.38 |
Transit providers
6 upstream, 92 downstream and 114 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-03, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 137 prefixes · 122K addresses IPv6 572 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 709 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS12025- Registry name
- IMDC-AS12025
- Registrant
- Iron Mountain Data Center
- Abuse contact
- imdc.abuse@ironmountain.com
- Registered
- 2007-05-30
- Last changed
- 2020-02-25
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Iron Mountain Data Centers (fka IO Data Centers)
- Also known as
- IMDC
- Network type
- NSP
- Scope
- North America
- Traffic ratio
- Balanced
- Peering policy
- Open
- IRR as-set
RADB::AS12025:AS-CONE- Present at
- 1 exchanges
- Facilities
- 4 facilities
- Website
- https://www.ironmountain.com/digital-transformation/data-centers
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 16% valid · 117 valid, 607 with no ROA
- ROAs
- 130 authorising AS12025
- ASPA
- no ASPA record
- IRR
- 100% registered · 724 of 724 announcements
- Route objects
- 291 naming AS12025
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 451 networks and 1,853 prefixes, as published 2026-11-04. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere