ixreport

FiberComm

AS54578

ImOn Communications, LLC

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

Tools: Where can I peer with FiberComm? · Where should FiberComm peer next? · Compare FiberComm with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in FiberComm's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-11-19 12:40 UTC.

Make the changes on FiberComm'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 FiberComm's PeeringDB record. Add one entry per connection with these values.

  1. United States SIOUIX Sioux City, United States · PeeringDB 4132From its IX-F export and website members list
    IPv4149.112.41.2
    IPv62001:504:126::2
    Speed10000 Mbps (10G)
    RS peerNot published

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 MICE Minneapolis, MN, United States · PeeringDB 446
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:504:27::d532:0:1
    • In the entry with IPv4 206.108.255.78: set IPv6 to 2001:504:27::d532:0:1 (now empty).

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If FiberComm has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United States OmahaIX Omaha, United States · PeeringDB 809Not on its website members list
    IPv4206.126.235.34
    IPv6–
    Speed100000 Mbps (100G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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 FiberComm'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 210G across 3 exchanges.

United States MICE Minneapolis, MN, United States 206.108.255.78 100G 14 routes Both IPv6 not in PeeringDB
United States OmahaIX Omaha, United States 206.126.235.34 100G PeeringDB only
United States SIOUIX Sioux City, United States 149.112.41.2 2001:504:126::2 10G Not in PeeringDB

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

These exchanges have a switch in a facility where FiberComm lists itself in PeeringDB, but don't have FiberComm 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 MIN1
United States KCIXKansas City, United States 216 Cologix MIN1
United States IX-DenverDenver, United States 96 Cologix MIN1
United States QCIXDavenport, United States 69 Cologix MIN1
United States SIX Seattle (Jumbo)Seattle, United States 69 Cologix MIN1
Facilities (3)

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

United States Cologix MIN1Minneapolis 1 of 6
United States 1623 Farnam - OmahaOmaha 1 of 1
United States 713 NebraskaSioux City No exchange