StarHub AS4657: PeeringDB fix list

AS4657 · peeringdb.com/net/1062

PeeringDB

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

Make the changes on StarHub AS4657'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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs5G10G
    • In the entry with IPv4 80.249.212.55: set Speed to 10000 (10G) (now 5000).

    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 differs5G400G
    • In the entry with IPv4 80.81.193.240: set Speed to 400000 (400G) (now 5000).
  3. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs5G10G
    • In the entry with IPv4 195.66.226.196: set Speed to 10000 (10G) (now 5000).

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