ixreport

Maharlika IX Route Servers: PeeringDB fix list

AS9420 · peeringdb.com/net/33246

PeeringDB

One thing to fix in Maharlika IX Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-09 06:39 UTC.

Make the changes on Maharlika IX 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 Maharlika IX Manila, Philippines · PeeringDB 4167
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export103.121.64.1 103.121.64.2 163.223.201.1 163.223.201.2163.223.201.1 163.223.201.2
    IPv6 address in PeeringDB, not in the export2001:df0:a940::9420:1 2001:df0:a940::9420:2 2400:efa0::9420:1 2400:efa0::9420:22001:df0:a940::9420:1 2001:df0:a940::9420:2
    • The entry with IPv4 103.121.64.1, IPv6 2400:efa0::9420:1 isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 103.121.64.2, IPv6 2400:efa0::9420:2 isn't in the export: delete it if that connection is gone.

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