asn.dev

Interconnection

AS44356 EPSILON

Unclassified APNIC

Exchanges 10 10 active
Countries 7 most in United States
Regions 4
Largest fabric 1,078 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

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

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.193.15Selective1,078
LINX LON1London, United Kingdom195.66.224.4Selective932
NAPAfrica IX JohannesburgJohannesburg, South Africa196.60.8.2Selective603
NAPAfrica IX Cape TownCape Town, South Africa196.60.70.99Selective311
JPIX TokyoTokyo, Japan210.171.224.115Selective301
DE-CIX New YorkNew York, United States206.82.104.157—285
Singapore Internet ExchangeSingapore, Singapore103.16.102.66Selective277
New York International Internet ExchangeNew York, United States198.32.160.68Selective214
Massachusetts Internet ExchangeBoston, United States206.53.143.49Selective73
AMS-IX Hong KongHong Kong, China103.247.139.4Route server only50

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