Interconnection

AS4862 EQUANT-ASIA Orange Business AS for Asia

Unclassified APNIC

Exchanges 9 9 active

Countries 6 most in India

Regions 1

Largest fabric 496 Equinix Internet Exchange Singapore

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS4862, 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 9

Exchange	Location	Their address	Policy	Member ports
Equinix Internet Exchange Singapore	Singapore, Singapore	27.111.229.115	Selective	496
BroadBand Internet eXchange Tokyo	Tokyo, Japan	101.203.89.65	Selective	361
Hong Kong Internet Exchange	Hong Kong, China	123.255.91.32	Selective	307
DE-CIX Mumbai	Mumbai, India	103.27.171.221	Open	277
Extreme IX Mumbai	Mumbai, India	103.77.108.182	Selective	245
Taipei Internet Exchange (TPIX)	Taipei, Taiwan	203.163.222.188	Selective	190
Extreme IX Chennai	Chennai, India	45.120.251.22	Selective	89
Korea Internet Neutral Exchange KINX	Seoul, South Korea	139.150.100.67	Selective	64
Network Service Provider IXP (Distributed IX in Edo)	Tokyo, Japan	202.249.2.41	Selective	27

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-11 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,138 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.