asn.dev

Interconnection

AS835 GOCODEIT-EDGE

Unclassified ARIN

Exchanges 12 11 active
Countries 5 most in United States
Regions 2
Largest fabric 932 LINX LON1

Recorded presence

Internet exchanges

recorded

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

North America 7 Europe 5

ExchangeLocationTheir addressPolicyMember ports
LINX LON1London, United Kingdom195.66.228.113Open932
Equinix Internet Exchange AshburnAshburn, United States206.126.239.94Open391
Seattle Internet ExchangeSeattle, United States206.81.81.53Open350
London Network Access PointLondon, United Kingdom5.57.82.167Open314
Toronto Internet ExchangeToronto, Canada206.108.35.161Open286
DE-CIX New YorkNew York, United States206.82.104.5Open285
Ontario Internet ExchangeToronto, Canada149.112.50.5Open205
ERA-IX AmsterdamAmsterdam, Netherlands185.1.240.167—199
Nine IXParis, France185.1.14.122—164
EuroGIX retiredStrasbourg, France185.1.14.122—129
Kansas City Internet ExchangeKansas City, United States206.51.7.247Open72
LINX NoVaReston, United States206.55.196.66Open48

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.