asn.dev

Interconnection

AS139967 YAMNET-AS-ID PT. Yasmin Amanah Media

Residential APNIC

Exchanges 12 12 active
Countries 2 most in Indonesia
Regions 1
Largest fabric 2,071 OpenIXP Internet exchange Point

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS139967, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's page, with its peering LANs and everyone else on it.

Asia-Pacific 12

ExchangeLocationTheir addressPolicyMember ports
OpenIXP Internet exchange PointJakarta, Indonesia218.100.36.240Open2,071
Indonesian Internet Exchange (IIX-Jakarta)Jakarta, Indonesia123.108.9.144Open953
Jakarta Internet ExchangeJakarta, Indonesia119.11.184.156Open833
Singapore Internet ExchangeSingapore, Singapore103.16.102.243Open278
Alien Internet ExchangeDepok, Indonesia43.254.82.81Open249
Omadata Internet Exchange (ODIX)Surabaya, Indonesia103.28.80.218Open223
cloudXchange JakartaJakarta, Indonesia103.225.173.32—207
DE-CIX JakartaJakarta, Indonesia49.213.56.12Open181
DE-CIX ASEAN (Singapore, Malaysia, Brunei)Singapore, Singapore103.162.254.154Open137
EdgeNXT Internet ExchangeJakarta, Indonesia103.61.232.98Open130
Digital Edge EPIX JakartaJakarta, Indonesia202.159.50.60Open86
Panda Internet ExchageSemarang, Indonesia165.101.31.10Open12

Recorded rather than inferred: an address on a peering LAN is at that exchange by definition. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. An absent exchange means PCH has no record of it, not that the network is not there. For the operator's own claims, see its PeeringDB record.

From the exchange directory collected 2026-10-14 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,276 recorded member ports, licensed CC BY-NC-SA 3.0.

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.