asn.dev

Interconnection

AS393891 NUTRIEN

Unclassified ARIN Enterprise

Exchanges 10 10 active
Countries 2 most in United States
Regions 1
Largest fabric 391 Equinix Internet Exchange Ashburn

Recorded presence

Internet exchanges

recorded

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

ExchangeLocationTheir addressPolicyMember ports
Equinix Internet Exchange AshburnAshburn, United States206.126.238.113Open391
Seattle Internet ExchangeSeattle, United States206.81.81.236Open350
Equinix Internet Exchange ChicagoChicago, United States208.115.137.13Open282
Equinix Internet Exchange San Jose (Bay Area)San Jose, United States206.223.116.66Open192
San Francisco Metropolitan Internet ExchangeSan Francisco, United States206.197.187.31Open109
YYCIX Calgary Internet ExchangeCalgary, Canada206.126.225.82Open102
Interconnection eXchange DenverDenver, United States206.53.175.56Open93
Equinix Internet Exchange SeattleSeattle, United States198.32.134.96Open45
Manitoba Internet ExchangeWinnipeg, Canada206.72.208.33Open28
YXEIX Saskatoon Internet ExchangeSaskatoon, Canada206.71.11.31Open25

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.