ixreport

Iron Mountain Data Centers (fka IO Data Centers)

AS12025 · IMDC

Iron Mountain Data Centers

3Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
3Using the route servers
2To fix in PeeringDB
4Facilities in PeeringDB

Tools: Where can I peer with Iron Mountain Data Centers (fka IO Data Centers)? · Where should Iron Mountain Data Centers (fka IO Data Centers) peer next? · Compare Iron Mountain Data Centers (fka IO Data Centers) with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Iron Mountain Data Centers (fka IO Data Centers)'s PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-11-19 18:41 UTC.

Make the changes on Iron Mountain Data Centers (fka IO Data Centers)'s PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (2)

On the exchange's own member list, but not in Iron Mountain Data Centers (fka IO Data Centers)'s PeeringDB record. Add one entry per connection with these values.

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18From its IX-F export and website members list
    IPv4195.66.231.219
    IPv62001:7f8:4::2ef9:1
    Speed10000 Mbps (10G)
    RS peerYes
  2. United States LINX NoVA Ashburn, Reston, Manassas, United States · PeeringDB 777From its IX-F export and website members list
    IPv4206.55.196.14
    IPv62001:504:31::2ef9:1
    Speed50000 Mbps (50G)
    RS peerYes

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where Iron Mountain Data Centers (fka IO Data Centers)'s exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 70G across 3 exchanges.

United States DE-CIX New York New York, United States 206.82.105.38 2001:504:36::2ef9:0:1 10G Down Both
United Kingdom LINX LON1 London, United Kingdom 195.66.231.219 2001:7f8:4::2ef9:1 10G Up, 0 routes Not in PeeringDB
United States LINX NoVA Ashburn, Reston, Manassas, United States 206.55.196.14 2001:504:31::2ef9:1 50G 1 routes Not in PeeringDB

Exchanges in its buildings that it isn't on (3)

These exchanges have a switch in a facility where Iron Mountain Data Centers (fka IO Data Centers) lists itself in PeeringDB, but don't have Iron Mountain Data Centers (fka IO Data Centers) as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (4)

The buildings Iron Mountain Data Centers (fka IO Data Centers) lists in PeeringDB, and how many of the exchanges in each it's on.

United States Iron Mountain Data Center - New Jersey (NJE-1)Edison 1 of 2
United States Iron Mountain Data Center - Phoenix (AZP-1)Phoenix 0 of 2
United States Iron Mountain Data Center - Scottsdale (AZS-1)Scottsdale 0 of 1
United States Iron Mountain Data Center - Ohio (OHS-1)Miamisburg No exchange