HGC: PeeringDB fix list

AS9304 · peeringdb.com/net/487

PeeringDB

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

Make the changes on HGC'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 differs10G2 × 10G

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

  2. Thailand AMS-IX Bangkok Bangkok, Thailand · PeeringDB 4232
    ProblemPeeringDB hasThe export has
    Port speed differs10G30G
    • In the entry with IPv4 103.100.140.47: set Speed to 30000 (30G) (now 10000).

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

  3. Hong Kong AMS-IX Hong Kong Hong Kong, Hong Kong · PeeringDB 577
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G + 30G + 10G
    • In the entry with IPv4 103.247.139.39: set Speed to 30000 (30G) (now 100000).

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

  4. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs30G100G
    • In the entry with IPv4 195.66.224.100: set Speed to 100000 (100G) (now 30000).

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