Fort Dodge Fiber: PeeringDB fix list

AS400405 · peeringdb.com/net/35744

PeeringDB

One thing to fix in Fort Dodge Fiber's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Fort Dodge Fiber'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 MICE Minneapolis, MN, United States · PeeringDB 446
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 206.108.255.229: set Speed to 20000 (20G) (now 10000).

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

From ixreport.com/net/400405/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.