FiberComm
AS54578
ImOn Communications, LLC
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.
-
IPv4 149.112.41.2 IPv6 2001:504:126::2 Speed 10000 Mbps (10G) RS peer Not 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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
IPv4 206.126.235.34 IPv6 – Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 3 |
| Nov 18, 2026 | 3 |
| Nov 17, 2026 | 3 |
| Nov 16, 2026 | 3 |
| Nov 15, 2026 | 3 |
| Nov 14, 2026 | 3 |
| Nov 13, 2026 | 3 |
| Nov 12, 2026 | 3 |
| Nov 11, 2026 | 3 |
| Nov 10, 2026 | 3 |
| Nov 9, 2026 | 3 |
| Nov 8, 2026 | 3 |
| Nov 7, 2026 | 3 |
| Nov 6, 2026 | 3 |
| Nov 5, 2026 | 3 |
| Nov 4, 2026 | 3 |
| Nov 3, 2026 | 3 |
| Nov 2, 2026 | 3 |
| Nov 1, 2026 | 3 |
| Oct 31, 2026 | 3 |
| Oct 30, 2026 | 3 |
| Oct 29, 2026 | 3 |
| Oct 28, 2026 | 3 |
| Oct 27, 2026 | 3 |
| Oct 26, 2026 | 3 |
| Oct 25, 2026 | 3 |
| Oct 24, 2026 | 3 |
| Oct 23, 2026 | 3 |
| Oct 22, 2026 | 3 |
| Oct 21, 2026 | 3 |
| Oct 20, 2026 | 3 |
| Oct 19, 2026 | 3 |
| Oct 18, 2026 | 3 |
| Oct 17, 2026 | 3 |
| Oct 16, 2026 | 3 |
| Oct 15, 2026 | 3 |
| Oct 14, 2026 | 3 |
| Oct 13, 2026 | 3 |
| Oct 12, 2026 | 3 |
| Oct 11, 2026 | 3 |
| Oct 10, 2026 | 3 |
| Oct 9, 2026 | 3 |
| Oct 8, 2026 | 3 |
| Oct 7, 2026 | 3 |
| Oct 6, 2026 | 3 |
| Oct 5, 2026 | 3 |
| Oct 4, 2026 | 3 |
| Oct 3, 2026 | 3 |
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.
| MICE Minneapolis, MN, United States | 100G | Both IPv6 not in PeeringDB | |
| OmahaIX Omaha, United States | 100G | PeeringDB only | |
| SIOUIX Sioux City, United States | 10G | Not in PeeringDB |
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.
| SIX SeattleSeattle, United States | 372 | |
| KCIXKansas City, United States | 216 | |
| IX-DenverDenver, United States | 96 | |
| QCIXDavenport, United States | 69 | |
| SIX Seattle (Jumbo)Seattle, United States | 69 |
Facilities (3)
The buildings FiberComm lists in PeeringDB, and how many of the exchanges in each it's on.
| Cologix MIN1Minneapolis | 1 of 6 | |
| 1623 Farnam - OmahaOmaha | 1 of 1 | |
| 713 NebraskaSioux City | No exchange |