ixreport

QTS Chicago

AS394968

QTS Realty Trust, Inc.

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

Tools: Where can I peer with QTS Chicago? · Where should QTS Chicago peer next? · Compare QTS Chicago 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 Chicago's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on QTS Chicago'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 (1)

On the exchange's own member list, but not in QTS Chicago's PeeringDB record. Add one entry per connection with these values.

  1. United States MegaIX Chicago Chicago, United States · PeeringDB 4507From its IX-F export
    IPv4206.53.206.14
    IPv62606:a980:0:d::e
    SpeedNot published
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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

United States ChIX Chicago, United States 206.41.110.54 2001:504:41:110::54 10G Yes Both
United States DE-CIX Chicago Chicago, United States 149.112.11.25 2001:504:102:0:6:6d8:0:1 10G 26 routes Both
United States MegaIX Chicago Chicago, United States 206.53.206.14 2606:a980:0:d::e Yes Not in PeeringDB

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

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

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

United States Equinix CH1/CH2/CH4 - ChicagoChicago 3 of 9
United States QTS Chicago (CHI1)Chicago 3 of 4