asn.dev

Internet exchange

Ninja-IX Las Vegas

active Las Vegas, United States

Recorded members 23 addresses on file
Connected ports 11 across all participants
Peak traffic 51.5 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
Las Vegas, United States
Region
North America
Status
Active
PCH record updated
2026-10-26

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.8.0/25IPv4Active11
2001:504:68::/64IPv6Active10

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

11 networks · 23 addresses

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. Each network's addresses on the fabric are listed together, IPv4 first. Typing in the box narrows the rows below; Search looks through all 23 recorded addresses.

ASNetworkAddressesrDNSPolicy
AS6939Hurricane Electric LLC206.71.8.102001:504:68::10——Open
AS13335Cloudflare, Inc.206.71.8.112001:504:68::11——Open
AS25152Reseaux IP Europeens Network Coordination Centre (RIPE NCC)206.71.8.192001:504:68::19——Open
AS47065USC UFMG PEERING Research Testbed206.71.8.172001:504:68::17——Open
AS112DNS-OARC206.71.8.122001:504:68::12——Open
AS53698Ninja-IX Corporation206.71.8.92001:504:68::9——Open
AS12233Ninja-IX Corporation206.71.8.8—Open
AS22486NINJA-IX CORP206.71.8.5206.71.8.62001:504:68::52001:504:68::6————Open
AS23456INTERNET ASSIGNED NAMES AUTHORITY206.71.8.32001:504:68::3———
AS30134INET SYS CONSORTIUM, INC.206.71.8.182001:504:68::18——Open
AS35940NINJA-IX CORP206.71.8.22001:504:68::2——Open

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-10-27 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,347 exchanges and 97,379 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.