asn.dev

Interconnection

AS8849 MELBICOM-EU-AS Melbikomas UAB

Hosting RIPE

Exchanges 11 11 active
Countries 7 most in India
Regions 4
Largest fabric 496 Equinix Internet Exchange Singapore

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS8849, 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 5 Africa 2 Europe 2 North America 2

ExchangeLocationTheir addressPolicyMember ports
Equinix Internet Exchange SingaporeSingapore, Singapore27.111.230.75Open496
Coresite - Any2 WestLos Angeles, United States206.72.211.117Open344
Any2 CaliforniaLos Angeles, United States206.72.211.117Open319
JPIX TokyoTokyo, Japan210.171.225.18Open301
DE-CIX MumbaiMumbai, India103.27.170.121Open277
Singapore Internet ExchangeSingapore, Singapore103.16.102.212Open277
Extreme IX MumbaiMumbai, India103.77.108.156Open243
Internet Exchange Point of Nigeria - LagosLagos, Nigeria196.216.148.80Open138
UAE-IXDubai, United Arab Emirates185.1.8.28Open113
AMS-IX LagosLagos, Nigeria196.60.58.226Open56
Netnod Sundsvall- GävleSundsvall, Sweden194.68.128.209Open18

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