ixreport

IX-Denver Tenant: PeeringDB fix list

AS399029 · peeringdb.com/net/32280

PeeringDB

One thing to fix in IX-Denver Tenant's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on IX-Denver Tenant'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 IX-Denver Denver, United States · PeeringDB 1207
    ProblemPeeringDB hasThe export has
    Port speed differs40G200G + 10G
    • In the entry with IPv4 206.53.175.100: set Speed to 200000 (200G) (now 40000).

    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/399029/: 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.