Midcontinent Communications
AS11232 · MIDCO-NET
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.
-
Problem PeeringDB has The export has Port speed differs 20G 10G - 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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 6 |
| Nov 18, 2026 | 6 |
| Nov 17, 2026 | 6 |
| Nov 16, 2026 | 6 |
| Nov 15, 2026 | 6 |
| Nov 14, 2026 | 6 |
| Nov 13, 2026 | 6 |
| Nov 12, 2026 | 6 |
| Nov 11, 2026 | 6 |
| Nov 10, 2026 | 6 |
| Nov 9, 2026 | 6 |
| Nov 8, 2026 | 6 |
| Nov 7, 2026 | 6 |
| Nov 6, 2026 | 6 |
| Nov 5, 2026 | 6 |
| Nov 4, 2026 | 6 |
| Nov 3, 2026 | 6 |
| Nov 2, 2026 | 6 |
| Nov 1, 2026 | 6 |
| Oct 31, 2026 | 6 |
| Oct 30, 2026 | 6 |
| Oct 29, 2026 | 6 |
| Oct 28, 2026 | 6 |
| Oct 27, 2026 | 6 |
| Oct 26, 2026 | 6 |
| Oct 25, 2026 | 6 |
| Oct 24, 2026 | 6 |
| Oct 23, 2026 | 6 |
| Oct 22, 2026 | 6 |
| Oct 21, 2026 | 6 |
| Oct 20, 2026 | 6 |
| Oct 19, 2026 | 6 |
| Oct 18, 2026 | 6 |
| Oct 17, 2026 | 6 |
| Oct 16, 2026 | 6 |
| Oct 15, 2026 | 6 |
| Oct 14, 2026 | 6 |
| Oct 13, 2026 | 6 |
| Oct 12, 2026 | 6 |
| Oct 11, 2026 | 6 |
| Oct 10, 2026 | 6 |
| Oct 9, 2026 | 6 |
| Oct 8, 2026 | 6 |
| Oct 7, 2026 | 6 |
| Oct 6, 2026 | 6 |
| Oct 5, 2026 | 6 |
| Oct 4, 2026 | 6 |
| Oct 3, 2026 | 6 |
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.
| Any2Denver Denver, United States | 100G | PeeringDB | |
| Equinix Chicago Chicago, United States | 200G | PeeringDB | |
| IX-Denver Denver, United States | 20G | Both Speed differs | |
| KCIX Kansas City, United States | 20G | Both | |
| MICE Minneapolis, MN, United States | 100G | Both | |
| OmahaIX Omaha, United States | 200G + 20G | Both |
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.
| SIX SeattleSeattle, United States | 372 | |
| NetIXSofia, Bulgaria | 204 | |
| DE-CIX ChicagoChicago, United States | 86 | |
| ChIXChicago, United States | 73 | |
| SIX Seattle (Jumbo)Seattle, United States | 69 | |
| JumboIX PeruLima, Peru | 27 | |
| MegaIX ChicagoChicago, United States | 13 | |
| Chicago Open PipesChicago, United States | 9 | |
| MegaIX DenverDenver, United States | 7 | |
| Global Peer ExchangeWashington, United States | 6 | |
| FD-IX - ChicagoChicago, United States | 4 |
Facilities (8)
The buildings Midcontinent Communications lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix CH1/CH2/CH4 - ChicagoChicago | 1 of 9 | |
| Cologix MIN3Minneapolis | 1 of 3 | |
| CoreSite - Denver (DE1)Denver | 2 of 3 | |
| Netrality Kansas City - 1102 GrandKansas City | 1 of 2 | |
| 1623 Farnam - OmahaOmaha | 1 of 1 | |
| Midco FargoFargo | No exchange | |
| Midco Grand ForksGrand Forks | No exchange | |
| Midco Sioux FallsSioux Falls | No exchange |