WebEx Communications: PeeringDB fix list

AS13445 · peeringdb.com/net/1517

PeeringDB

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

Make the changes on WebEx Communications'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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs200G100G
    • In the entry with IPv4 80.249.208.75: set Speed to 100000 (100G) (now 200000).

    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
    IPv4 address missing from PeeringDB80.81.194.10580.81.194.105 80.81.197.7
    IPv6 address missing from PeeringDB2001:7f8::3485:0:12001:7f8::3485:0:1 2001:7f8::3485:0:2
    • Add an entry: IPv4 80.81.197.7, IPv6 2001:7f8::3485:0:2, speed 100000 (100G), RS peer yes.
  3. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    Port speed differs20G40G
    • In the entry with IPv4 103.27.171.6: set Speed to 40000 (40G) (now 20000).
  4. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs200G100G
    • In the entry with IPv4 195.66.225.110: set Speed to 100000 (100G) (now 200000).

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