ixreport

RNDS Network: PeeringDB fix list

AS154180 · peeringdb.com/net/40209

PeeringDB

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

Make the changes on RNDS Network'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 (2)

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. Philippines GetaFIX Manila Manila, Philippines · PeeringDB 2345
    ProblemPeeringDB hasThe export has
    Port speed differs20G10G
    • In the entry with IPv4 103.104.19.156: set Speed to 10000 (10G) (now 20000).

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

  2. Philippines Maharlika IX Manila, Philippines · PeeringDB 4167
    ProblemPeeringDB hasThe export has
    IPv4 address differs103.121.64.70163.223.201.70
    IPv6 address differs2400:efa0::15:4180:12001:df0:a940::15:4180:1
    • In the entry with IPv4 103.121.64.70: set IPv4 to 163.223.201.70 (now 103.121.64.70); set IPv6 to 2001:df0:a940::15:4180:1 (now 2400:efa0::15:4180:1).

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