ixreport

F4IX MCI Route Servers

AS36090 · F4IX MCI

F4 Networks

1Exchange
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Route ServerType
OpenPeering policy
1Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with F4IX MCI Route Servers? · Where should F4IX MCI Route Servers peer next? · Compare F4IX MCI Route Servers with another network

This network elsewhere: its registry history on RIR Tracker

PeeringDB fix list Printable page · CSV

One thing to fix in F4IX MCI Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on F4IX MCI Route Servers'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 F4IX MCI Kansas City, United States · PeeringDB 4378
    ProblemPeeringDB hasThe export has
    Port speed differs40G + 10G100G + 40G
    • In the entry with IPv4 149.112.75.1: set Speed to 100000 (100G) (now 40000).
    • In the entry with IPv4 149.112.75.2: set Speed to 40000 (40G) (now 10000).

    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

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

Map

Where F4IX MCI Route Servers'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 50G across 1 exchange.

United States F4IX MCI Kansas City, United States 149.112.75.1
149.112.75.2
2602:fa3d:f4:1::1
2602:fa3d:f4:1::2
40G + 10G Yes Both Speed differs

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

These exchanges have a switch in a facility where F4IX MCI Route Servers lists itself in PeeringDB, but don't have F4IX MCI Route Servers 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 1530 SWIFT - NOCIX
United States KCIXKansas City, United States 216 1530 SWIFT - NOCIX
United States MICEMinneapolis, MN, United States 157 1530 SWIFT - NOCIX
United States STLIXSaint Louis, MO, United States 108 1530 SWIFT - NOCIX
United States IX-DenverDenver, United States 96 1530 SWIFT - NOCIX
United States HOUIXHouston, United States 81 1530 SWIFT - NOCIX
United States SIX Seattle (Jumbo)Seattle, United States 69 1530 SWIFT - NOCIX
United States HN Internet Exchange (Main)North Kansas City, United States 27 1530 SWIFT - NOCIX
United States SpringIXSpringfield, MO, United States 22 1530 SWIFT - NOCIX
United States DesMoinesIXDes Moines, United States 11 1530 SWIFT - NOCIX
United States SIOUIXSioux City, United States 4 1530 SWIFT - NOCIX
United States MOCIXKansas City, United States 3 1530 SWIFT - NOCIX
Facilities (1)

The buildings F4IX MCI Route Servers lists in PeeringDB, and how many of the exchanges in each it's on.

United States 1530 SWIFT - NOCIXNorth Kansas City 1 of 13