ixreport

Agarto: PeeringDB fix list

AS56111 · peeringdb.com/net/3969

PeeringDB

3 things to fix in Agarto's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Agarto'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 (3)

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. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 500M20G + 10G
    • In the entry with IPv4 103.162.254.18: set Speed to 20000 (20G) (now 500).
    • In the entry with IPv4 103.162.254.42: set Speed to 10000 (10G) (now 500).
  2. Malaysia DE-CIX Kuala Lumpur Kuala Lumpur, Malaysia · PeeringDB 3473
    ProblemPeeringDB hasThe export has
    Port speed differs10G + 5G20G + 10G
    • In the entry with IPv4 103.119.234.16: set Speed to 20000 (20G) (now 10000).
    • In the entry with IPv4 103.119.234.30: set Speed to 10000 (10G) (now 5000).
  3. Malaysia Penang IX Penang, Malaysia · PeeringDB 4269
    ProblemPeeringDB hasThe export has
    Port speed differs1G20G
    • In the entry with IPv4 103.10.57.11: set Speed to 20000 (20G) (now 1000).

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