asn.dev

Internet exchange

AMS-IX Manila

active Manila, Philippines

Recorded members 26 addresses on file
Connected ports 11 across all participants
Peak traffic 18.6 Mbps peak, as recorded
Peering LANs 2 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
Manila, Philippines
Region
Asia-Pacific
Status
Active
PCH record updated
2026-08-07

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

2 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
112.137.26.0/24IPv4Active11
2407:b140:ae5::/64IPv6Active11

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

26 shown

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. One row per recorded address, so a network running dual-stack appears once for its IPv4 interface and once for its IPv6 one.

ASNetworkAddressrDNSPolicy
AS9304HGC Global Communications Limited112.137.26.6Case-by-case
AS9304HGC Global Communications Limited2407:b140:ae5::a500:9304:1Case-by-case
AS4775Globe Telecoms2407:b140:ae5::a500:4775:1Open
AS4775Globe Telecoms112.137.26.166Open
AS139341ACE112.137.26.223Open
AS139341ACE2407:b140:ae5:0:a500:13:9341:1Open
AS32934Facebook, Inc.2407:b140:ae5::a503:2934:2Open
AS32934Facebook, Inc.2407:b140:ae5::a503:2934:1Open
AS32934Facebook, Inc.112.137.26.147Open
AS32934Facebook, Inc.112.137.26.43ae1004.pr02.mnl2.tfbnw.netOpen
AS9658Eastern Telecoms Phils., Inc.2407:b140:ae5::a500:9658:1Case-by-case
AS9658Eastern Telecoms Phils., Inc.112.137.26.133Case-by-case
AS18187Ignite Telecommunications Inc112.137.26.13Open
AS18187Ignite Telecommunications Inc2407:b140:ae5::a501:8187:1Open
AS153174Aioni Digital and Data Solutions Inc.112.137.26.230Open
AS153174Aioni Digital and Data Solutions Inc.2407:b140:ae5:0:a500:15:3174:1Open
AS137996HGC Global Communications (Philippines), Inc.112.137.26.36Open
AS137996HGC Global Communications (Philippines), Inc.2407:b140:ae5:0:a500:13:7996:1Open
AS134802Naic Cable TV Corp.2407:b140:ae5:0:a500:13:4802:1Open
AS134802Naic Cable TV Corp.112.137.26.228Open
AS135582Galaxy Cable Corp.2407:b140:ae5:0:a500:13:5582:1Open
AS135582Galaxy Cable Corp.112.137.26.128Open
AS137527HGC GLOBAL COMM , INC.2407:b140:ae5:0:a500:13:7527:251Open
AS137527HGC GLOBAL COMM , INC.2407:b140:ae5:0:a500:13:7527:252Open
AS137527HGC GLOBAL COMM , INC.112.137.26.251rs1-mng.mnl.ams-ix.netOpen
AS137527HGC GLOBAL COMM , INC.112.137.26.252rs2-mng.mnl.ams-ix.netOpen

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-08-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.