ixreport

Sho Me Technologies: PeeringDB fix list

AS55140 · peeringdb.com/net/17170

PeeringDB

2 things to fix in Sho Me Technologies's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Sho Me Technologies'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 (2)

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 KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.51.7.78206.51.7.78 206.51.7.245
    IPv6 address missing from PeeringDB2001:504:1b:1::782001:504:1b:1::78 2001:504:1b:1::245
    Port speed differs100G100G + 10G
    • In the entry with IPv4 206.51.7.78: set Speed to 10000 (10G) (now 100000).
    • Add an entry: IPv4 206.51.7.245, IPv6 2001:504:1b:1::245, speed 100000 (100G).
  2. United States STLIX Saint Louis, MO, United States · PeeringDB 2585
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 206.83.12.22: set Speed to 10000 (10G) (now 100000).

From ixreport.com/net/55140/: 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.