ixreport

Midcontinent Communications

AS11232 · MIDCO-NET

6Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
SelectivePeering policy
6Using the route servers
1To fix in PeeringDB
8Facilities in PeeringDB

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

Make the changes on Midcontinent Communications'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 IX-Denver Denver, United States · PeeringDB 1207
    ProblemPeeringDB hasThe export has
    Port speed differs20G10G
    • In the entry with IPv4 206.53.175.85: set Speed to 10000 (10G) (now 20000).

    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

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

Map

Where Midcontinent Communications'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 660G across 6 exchanges.

United States Any2Denver Denver, United States 206.51.46.92 2605:6c00:303:303::92 100G Yes PeeringDB
United States Equinix Chicago Chicago, United States 208.115.136.166 2001:504:0:4:0:1:1232:1 200G Yes PeeringDB
United States IX-Denver Denver, United States 206.53.175.85 2001:504:58::85 20G Yes Both Speed differs
United States KCIX Kansas City, United States 206.51.7.145 2001:504:1b:1::145 20G Yes Both
United States MICE Minneapolis, MN, United States 206.108.255.170 2001:504:27::2be0:0:1 100G 279 routes Both
United States OmahaIX Omaha, United States 206.126.235.27
206.126.235.45
2001:504:33::21
2001:504:33::39
200G + 20G Yes Both

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

These exchanges have a switch in a facility where Midcontinent Communications lists itself in PeeringDB, but don't have Midcontinent Communications 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 SIX SeattleSeattle, United States 372 Cologix MIN3
Bulgaria NetIXSofia, Bulgaria 204 Equinix CH1/CH2/CH4 - Chicago; Netrality Kansas City - 1102 Grand
United States DE-CIX ChicagoChicago, United States 86 Equinix CH1/CH2/CH4 - Chicago
United States ChIXChicago, United States 73 Equinix CH1/CH2/CH4 - Chicago
United States SIX Seattle (Jumbo)Seattle, United States 69 Cologix MIN3
Peru JumboIX PeruLima, Peru 27 Equinix CH1/CH2/CH4 - Chicago
United States MegaIX ChicagoChicago, United States 13 Equinix CH1/CH2/CH4 - Chicago
United States Chicago Open PipesChicago, United States 9 Equinix CH1/CH2/CH4 - Chicago
United States MegaIX DenverDenver, United States 7 CoreSite - Denver (DE1)
United States Global Peer ExchangeWashington, United States 6 Equinix CH1/CH2/CH4 - Chicago
United States FD-IX - ChicagoChicago, United States 4 Equinix CH1/CH2/CH4 - Chicago
Facilities (8)

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

United States Equinix CH1/CH2/CH4 - ChicagoChicago 1 of 9
United States Cologix MIN3Minneapolis 1 of 3
United States CoreSite - Denver (DE1)Denver 2 of 3
United States Netrality Kansas City - 1102 GrandKansas City 1 of 2
United States 1623 Farnam - OmahaOmaha 1 of 1
United States Midco FargoFargo No exchange
United States Midco Grand ForksGrand Forks No exchange
United States Midco Sioux FallsSioux Falls No exchange