ixreport

QTS Richmond

AS53907

QTS Realty Trust, Inc.

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

Tools: Where can I peer with QTS Richmond? · Where should QTS Richmond peer next? · Compare QTS Richmond with another network

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

PeeringDB fix list Printable page · CSV

One thing to fix in QTS Richmond's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on QTS Richmond's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. United States DE-CIX Richmond Ashland, United States · PeeringDB 1002
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:504:44::5:3907:12001:504:44::d293:0:1
    • In the entry with IPv4 206.53.137.38: set IPv6 to 2001:504:44::d293:0:1 (now 2001:504:44::5:3907:1).

Exchanges over time

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

Map

Where QTS Richmond'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 30G, at the 3 of 4 exchanges with a speed in PeeringDB or the exchange's IX-F export.

United States DE-CIX Richmond Ashland, United States 206.53.137.38 2001:504:44::5:3907:1 10G 44 routes Both IPv6 differs
United States LINX NoVA Ashburn, Reston, Manassas, United States 206.55.197.243 2001:504:31::d293:1 10G 4 routes Both
United States MegaIX Ashburn Ashburn, United States 206.53.170.36 2606:a980:0:3::24 Yes Both
United States Ninja-IX Richmond Richmond, United States 206.71.9.11 2001:504:79::11 10G 46 routes Both

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

These exchanges have a switch in a facility where QTS Richmond lists itself in PeeringDB, but don't have QTS Richmond 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.

United States Equinix AshburnAshburn, United States 347 Equinix DC1-DC15,DC21-DC22 - Ashburn
Bulgaria NetIXSofia, Bulgaria 204 Equinix DC1-DC15,DC21-DC22 - Ashburn
United States NVIXAshburn, United States 78 Equinix DC1-DC15,DC21-DC22 - Ashburn
United States CIX-NoVAAshburn, Reston, Washington DC, United States 34 Equinix DC1-DC15,DC21-DC22 - Ashburn
United States DACS-IX EastWashington DC, United States 15 Equinix DC1-DC15,DC21-DC22 - Ashburn
United States Global Peer ExchangeWashington, United States 6 Equinix DC1-DC15,DC21-DC22 - Ashburn
United States GNM-IX USNew York, United States 4 Equinix DC1-DC15,DC21-DC22 - Ashburn
Facilities (2)

The buildings QTS Richmond lists in PeeringDB, and how many of the exchanges in each it's on.

United States Equinix DC1-DC15,DC21-DC22 - AshburnAshburn 2 of 9
United States QTS Richmond (RIC1)Sandston 3 of 3