ixreport

7Hoop Network Telecom, LLC: PeeringDB fix list

AS63066 · peeringdb.com/net/36715

PeeringDB

4 things to fix in 7Hoop Network Telecom, LLC's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on 7Hoop Network Telecom, LLC'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 (4)

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 differs200G80G
    • In the entry with IPv4 206.83.136.60: set Speed to 80000 (80G) (now 200000).
  2. United States KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G2 × 100G
    • In the entry with IPv4 206.51.7.204: set Speed to 100000 (100G) (now 200000).
    • In the entry with IPv4 206.51.7.225: set Speed to 100000 (100G) (now 200000).
  3. United States SpringIX Springfield, MO, United States · PeeringDB 3195
    ProblemPeeringDB hasThe export has
    Port speed differs200G80G
    • In the entry with IPv4 149.112.4.15: set Speed to 80000 (80G) (now 200000).

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

  4. United States STLIX Saint Louis, MO, United States · PeeringDB 2585
    ProblemPeeringDB hasThe export has
    Port speed differs200G80G
    • In the entry with IPv4 206.83.12.90: set Speed to 80000 (80G) (now 200000).

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