KCFiber: PeeringDB fix list
AS11708 · peeringdb.com/net/9261
5 things to fix in KCFiber's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on KCFiber'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 (2)
On the exchange's own member list, but not in KCFiber's PeeringDB record. Add one entry per connection with these values.
-
IPv4 149.112.41.3 IPv6 2001:504:126::3 Speed 10000 Mbps (10G) RS peer Not published -
SpringIX Springfield, MO, United States · PeeringDB 3195From its IX-F export and website members listIPv4 149.112.4.2 IPv6 2001:504:100::2 Speed 10000 Mbps (10G) RS peer Not published PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Correct these entries (3)
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 10G 100G - In the entry with IPv4 206.53.202.50: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 206.82.104.203: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:504:110::2 - In the entry with IPv4 149.112.17.2: set IPv6 to 2001:504:110::2 (now empty).
From ixreport.com/net/11708/: 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.