ixreport

CMC Telecom: PeeringDB fix list

AS45903 · peeringdb.com/net/3527

PeeringDB

3 things to fix in CMC Telecom's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on CMC Telecom'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 (1)

On the exchange's own member list, but not in CMC Telecom's PeeringDB record. Add one entry per connection with these values.

  1. Japan JPNAP Tokyo Tokyo, Japan · PeeringDB 95From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 80.249.215.154: set Speed to 10000 (10G) (now 1000).

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

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 80.81.193.8: set Speed to 100000 (100G) (now 10000).

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