ixreport

Metro Communications Company, Inc.

AS53610

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

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

Make the changes on Metro Communications Company, Inc.'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 STLIX Saint Louis, MO, United States · PeeringDB 2585
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 206.83.12.44: set Speed to 10000 (10G) (now 100000).

Exchanges over time

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

Map

Where Metro Communications Company, Inc.'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 700G across 5 exchanges.

United States ChIX Chicago, United States 206.41.110.30 2001:504:41:110::30 100G Yes Both
United States DE-CIX Chicago Chicago, United States 149.112.11.23 2001:504:102::d16a:0:1 200G 158 routes Both
United States Equinix Chicago Chicago, United States 208.115.137.11 2001:504:0:4:0:5:3610:1 200G Yes PeeringDB
United States KCIX Kansas City, United States 206.51.7.164 2001:504:1b:1::164 100G Yes Both
United States STLIX Saint Louis, MO, United States 206.83.12.44 2001:504:98::44 100G Yes Both Speed differs

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

These exchanges have a switch in a facility where Metro Communications Company, Inc. lists itself in PeeringDB, but don't have Metro Communications Company, Inc. 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 (3)

The buildings Metro Communications Company, Inc. 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 Digital Realty CHI (350 E Cermak)Chicago 3 of 6
United States Netrality St. Louis - 900 WalnutSt. Louis 2 of 4