Manila · Philippines
PeeringDB records six internet exchanges in Manila with 345 participant records between them. GetaFIX Manila is the best connected at 125 participants, ahead of BBIX Manila at 97 and MHK-IX at 53. One facility, PLDT Diliman, lists two networks. A Manila IP address shows where an operator registered a block, not where a device sits.
Internet exchanges in Manila
An exchange is a shared switch where networks hand traffic to each other directly. Participant counts come from PeeringDB, where each network maintains its own record.
| Exchange | Participants | Registry carriers peering |
|---|---|---|
GetaFIX Manila GetaFIX Manila - Philippines | 125 | |
BBIX Manila | 97 | |
MHK-IX Maharlika Internet Exchange | 53 | none in the registry |
PhOpenIX-Manila Philippine Open Internet Exchange (Manila) | 47 | |
PhIX | 12 | none in the registry |
AMS-IX Manila Amsterdam Internet Exchange Manila | 11 | none in the registry |
Exchange records: PeeringDB.
Colocation facilities
Buildings where networks put equipment. The network count is how many PeeringDB members list a presence there, which shows where capacity in the city sits.
| Facility | Networks present | Address |
|---|---|---|
| PLDT Diliman | 2 | 8003-A East Ave |
What a Manila IP address tells you
Manila's weight in PeeringDB sits in its exchanges rather than in colocation. Six exchanges add up to 345 participant records, and the top two hold most of that count: GetaFIX Manila at 125 participants and BBIX Manila at 97. MHK-IX follows with 53 and PhOpenIX-Manila with 47, while PhIX and AMS-IX Manila stay small at 12 and 11. Only one facility, PLDT Diliman, has an entry, and it lists two networks. AS4637 is flagged as a carrier ASN at three of the six exchanges; the registry names no mobile operators for the Philippines, so it cannot say which of them peer here.
An address that geolocates to Manila may not be a device in Manila. Operators announce address blocks from a registry record, and that record carries one city for a range the network can use anywhere it reaches. Mobile traffic leaves through a small number of gateways, so handsets spread across several provinces can exit behind the same Manila-registered addresses. Geolocation databases follow the operator's own published location, which means they repeat the filing rather than measure where a handset is.
Someone checking an address learns more from the origin ASN and the netname on the specific prefix than from the city label. The origin ASN names the network announcing the block, and the netname usually shows whether the range is a mobile pool or a hosting allocation. Set that against the six exchanges above and you can see whether the announcing network peers in Manila at all. The city string on its own says nothing about the equipment behind the address.
Questions
Which internet exchanges are in Manila?
PeeringDB lists six. GetaFIX Manila has 125 participants, BBIX Manila 97, MHK-IX 53, PhOpenIX-Manila 47, PhIX 12 and AMS-IX Manila 11. Together they account for 345 participant records, which makes Manila the city where Philippine exchange capacity is concentrated in this dataset.
Do Philippine mobile carriers peer in Manila?
The registry entry used here names no mobile operators for the Philippines, so the data cannot confirm which carriers peer locally. One carrier ASN, AS4637, appears at three of the six Manila exchanges. Anything beyond that has to come from each operator's own PeeringDB record.
Does an IP that geolocates to Manila mean the device is there?
No. The city comes from the operator's registry record for the address block, and geolocation databases copy that record. A mobile range registered in Manila can serve subscribers well outside the city, so read the label as the operator's filing rather than a position.
Sources
- PeeringDB - exchanges, participant counts, facilities and network presence, snapshot 2026-09-07
- PROXIES.SX carrier and ASN registry - operator ASNs used to match peering participants