Interconnection
AS62856 DOCUS-6-PROD
Hosting ARIN
Recorded presence
Internet exchanges
Internet exchanges where Packet Clearing House has a port recorded for AS62856, 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.
Europe 7 North America 5
| Exchange | Location | Their address | Policy | Member ports |
|---|---|---|---|---|
| DE-CIX Frankfurt | Frankfurt, Germany | 80.81.196.117 | No | 1,078 |
| LINX LON1 | London, United Kingdom | 195.66.231.101 | No | 932 |
| AMS-IX Amsterdam | Amsterdam, Netherlands | 80.249.214.166 | Open | 882 |
| Equinix Internet Exchange Ashburn | Ashburn, United States | 206.126.238.196 | No | 391 |
| Seattle Internet Exchange | Seattle, United States | 206.81.81.243 | — | 350 |
| Equinix Internet Exchange Chicago | Chicago, United States | 208.115.137.15 | No | 282 |
| Equinix Internet Exchange Paris | Paris, France | 195.42.144.5 | No | 236 |
| DE-CIX Dusseldorf | Düsseldorf, Germany | 185.1.170.131 | No | 227 |
| DE-CIX Munich | Munich, Germany | 185.1.209.1 | No | 211 |
| DE-CIX Hamburg | Hamburg, Germany | 185.1.210.197 | No | 196 |
| DE-CIX Dallas | Dallas, United States | 206.53.202.48 | No | 176 |
| LINX NoVa | Reston, United States | 206.55.196.8 | No | 48 |
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.