Telcotech Cambodia: PeeringDB fix list

AS55329 · peeringdb.com/net/3193

PeeringDB

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

Make the changes on Telcotech Cambodia'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 differs1G500M
    • In the entry with IPv4 80.249.214.62: set Speed to 500 (500M) (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. Hong Kong AMS-IX Hong Kong Hong Kong, Hong Kong · PeeringDB 577
    ProblemPeeringDB hasThe export has
    Port speed differs1G500M
    • In the entry with IPv4 103.247.139.29: set Speed to 500 (500M) (now 1000).

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

  3. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs1G400G
    • In the entry with IPv4 80.81.196.187: set Speed to 400000 (400G) (now 1000).
  4. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs1G300M
    • In the entry with IPv4 195.66.225.244: set Speed to 300 (300M) (now 1000).

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