GetaFIX.ph Route Servers: PeeringDB fix list

AS23942 · peeringdb.com/net/17721

PeeringDB

3 things to fix in GetaFIX.ph Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct, 2 to check. As of 2026-10-08 20:58 UTC.

Make the changes on GetaFIX.ph Route Servers'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 (1)

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 Davao Davao, Philippines · PeeringDB 4327
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 20G20G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If GetaFIX.ph Route Servers has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Philippines GetaFIX Cebu Cebu, Philippines · PeeringDB 3558Not on its IX-F export
    IPv4116.89.244.1
    IPv62401:fdc0:0:1:0:2:3942:1
    Speed20000 Mbps (20G)
    IPv4116.89.244.2
    IPv62401:fdc0:0:1:0:2:3942:2
    Speed20000 Mbps (20G)
  2. Philippines GetaFIX Manila Manila, Philippines · PeeringDB 2345Not on its IX-F export
    IPv4103.104.19.1
    IPv62401:fdc0::2:3942:1
    Speed20000 Mbps (20G)
    IPv4103.104.19.2
    IPv62401:fdc0::2:3942:2
    Speed20000 Mbps (20G)

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