Evalse: PeeringDB fix list

AS40916 · peeringdb.com/net/24416

PeeringDB

2 things to fix in Evalse's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Evalse'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 HOUIX Houston, United States · PeeringDB 2835
    ProblemPeeringDB hasThe export has
    Port speed differs40G1G
    • In the entry with IPv4 206.83.136.49: set Speed to 1000 (1G) (now 40000).
  2. United States STLIX Saint Louis, MO, United States · PeeringDB 2585
    ProblemPeeringDB hasThe export has
    Port speed differs40G1G
    • In the entry with IPv4 206.83.12.79: set Speed to 1000 (1G) (now 40000).

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