ixreport

Maharlika IX Route Servers

AS9420

Maharlika IX

1Exchange
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Route ServerType
OpenPeering policy
0Using the route servers
1To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with Maharlika IX Route Servers? · Where should Maharlika IX Route Servers peer next? · Compare Maharlika IX Route Servers with another network

This network elsewhere: its registry history on RIR Tracker

PeeringDB fix list Printable page · CSV

One thing to fix in Maharlika IX Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 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.

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

Exchanges over time

01Oct 3, 2026Nov 19, 20261
Show as a table
DateExchanges
Nov 19, 20261
Nov 18, 20261
Nov 17, 20261
Nov 16, 20261
Nov 15, 20261
Nov 14, 20261
Nov 13, 20261
Nov 12, 20261
Nov 11, 20261
Nov 10, 20261
Nov 9, 20261
Nov 8, 20261
Nov 7, 20261
Nov 6, 20261
Nov 5, 20261
Nov 4, 20261
Nov 3, 20261
Nov 2, 20261
Nov 1, 20261
Oct 31, 20261
Oct 30, 20261
Oct 29, 20261
Oct 28, 20261
Oct 27, 20261
Oct 26, 20261
Oct 25, 20261
Oct 24, 20261
Oct 23, 20261
Oct 22, 20261
Oct 21, 20261
Oct 20, 20261
Oct 19, 20261
Oct 18, 20261
Oct 17, 20261
Oct 16, 20261
Oct 15, 20261
Oct 14, 20261
Oct 13, 20261
Oct 12, 20261
Oct 11, 20261
Oct 10, 20261
Oct 9, 20261
Oct 7, 20261
Oct 6, 20261
Oct 5, 20261
Oct 4, 20261
Oct 3, 20261

Map

Where Maharlika IX Route Servers's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 40G across 1 exchange.

Philippines Maharlika IX Manila, Philippines 103.121.64.1
103.121.64.2
163.223.201.1
163.223.201.2
2001:df0:a940::9420:1
2001:df0:a940::9420:2
2400:efa0::9420:1
2400:efa0::9420:2
4 × 10G Both IPv4 not in exportIPv6 not in export

Exchanges in its buildings that it isn't on (9)

These exchanges have a switch in a facility where Maharlika IX Route Servers lists itself in PeeringDB, but don't have Maharlika IX Route Servers as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (3)

The buildings Maharlika IX Route Servers lists in PeeringDB, and how many of the exchanges in each it's on.

Philippines VITRO Makati 2Makati 1 of 8
Philippines STT Makati (Formerly MK2)Makati 1 of 7
Philippines VITRO Makati 1 - Yuchengco TowerMakati 1 of 5

Recent changes Search them

  • Oct 9, 2026 [PDB] [IXF] AS9420 Maharlika IX Route Servers added to Maharlika IX
  • Oct 8, 2026 [PDB] AS9420 left Maharlika IX