asn.dev

Internet exchange

Ninja-IX Richmond

active Richmond, United States

Recorded members 21 addresses on file
Connected ports 10 across all participants
Peak traffic 7.3 Mbps peak, as recorded
Peering LANs 2 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
Richmond, United States
Region
North America
Status
Active
PCH record updated
2026-08-08

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

2 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
206.71.9.0/25IPv4Active10
2001:504:79::/64IPv6Active9

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

21 shown

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. One row per recorded address, so a network running dual-stack appears once for its IPv4 interface and once for its IPv6 one.

ASNetworkAddressrDNSPolicy
AS6939Hurricane Electric LLC206.71.9.13he.richmond.ix.ninja-ix.netOpen
AS6939Hurricane Electric LLC2001:504:79::13Open
AS1828Unitas Global2001:504:79::14Selective
AS1828Unitas Global206.71.9.14unitas.richmond.ix.ninja-ix.netSelective
AS112DNS-OARC2001:504:79::12Open
AS112DNS-OARC206.71.9.12as112.richmond.ix.ninja-ix.netOpen
AS53907Quality Technology Services, LLC206.71.9.11qts.richmond.ix.ninja-ix.netOpen
AS53907Quality Technology Services, LLC2001:504:79::11Open
AS53698Ninja-IX Corporation206.71.9.9ninja-ix-transit.richmond.ix.ninja-ix.netOpen
AS53698Ninja-IX Corporation2001:504:79::9Open
AS12233Ninja-IX Corporation206.71.9.8Open
AS23456INTERNET ASSIGNED NAMES AUTHORITY2001:504:79::3
AS23456INTERNET ASSIGNED NAMES AUTHORITY206.71.9.3smokeping.richmond.ix.ninja-ix.net
AS26628RICHMOND-IX CORP206.71.9.6rs2.richmond.ix.ninja-ix.netOpen
AS26628RICHMOND-IX CORP2001:504:79::5Open
AS26628RICHMOND-IX CORP206.71.9.5rs1.richmond.ix.ninja-ix.netOpen
AS26628RICHMOND-IX CORP2001:504:79::6Open
AS33076INET SYS CONSORTIUM, INC.2001:504:79::18Open
AS33076INET SYS CONSORTIUM, INC.206.71.9.18froot.richmond.ix.ninja-ix.netOpen
AS35940NINJA-IX CORP2001:504:79::2Open
AS35940NINJA-IX CORP206.71.9.2lg.richmond.ix.ninja-ix.netOpen

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. 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.