asn.dev

Interconnection

AS53698 NINJA-IX-TRANSIT-CONNECTION

Unclassified ARIN

Exchanges 8 8 active
Countries 1 most in United States
Regions 1
Largest fabric 62 Ninja-IX Phoenix

Recorded presence

Internet exchanges

recorded

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

ExchangeLocationTheir addressPolicyMember ports
Ninja-IX PhoenixPhoenix, United States206.41.105.9Open62
Ninja-IX Las VegasLas Vegas, United States206.71.8.9Open11
Ninja-IX RichmondRichmond, United States206.71.9.9Open10
Ninja-IX DallasDallas, United States206.71.139.9Open9
Ninja-IX SacramentoSacramento, United States206.71.13.9Open7
Ninja-IX RaleighRaleigh, United States206.80.232.9Open6
Ninja-IX AuburnAuburn, CA, United States149.112.25.9Open5
Ninja-IX CharlotteCharlotte, United States206.71.143.9Open4

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