asn.dev

Internet exchange

Central Oregon Internet eXchange

active Bend, United States RDM

Recorded members 30 addresses on file
Connected ports 14 across all participants
Peak traffic 630 kbps 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
Bend, United States
Region
North America
Airport code
RDM
Status
Active
PCH record updated
2026-10-11

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
149.112.8.0/24IPv4Active14
2001:504:101::/64IPv6Active14

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

14 networks · 30 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 30 recorded addresses.

ASNetworkAddressesrDNSPolicy
AS42WoodyNet, Inc.149.112.8.122001:504:101::12as42.centraloregonix.org—Open
AS25899LS Networks149.112.8.52001:504:101::5as25899.centraloregonix.org—Open
AS25152Reseaux IP Europeens Network Coordination Centre (RIPE NCC)149.112.8.72001:504:101::7as25152.centraloregonix.org—Open
AS3856Packet Clearing House, Inc.149.112.8.132001:504:101::13as3856.centraloregonix.org—Open
AS397423Tier.Net Technologies LLC149.112.8.32001:504:101::3as397423.centraloregonix.org—Open
AS3701University of Oregon149.112.8.112001:504:101::11as3701.centraloregonix.org—Selective
AS55039Fatbeam, LLC149.112.8.92001:504:101::9as55039.centraloregonix.org—Selective
AS397373H4Y Technologies LLC149.112.8.42001:504:101::4as397373.centraloregonix.org—Open
AS27008BendTel149.112.8.102001:504:101::10as27008.centraloregonix.org—Open
AS11080Yellowknife Wireless Company, LLC149.112.8.62001:504:101::6as11080.centraloregonix.org—Open
AS35929Bend-La Pine Schools149.112.8.142001:504:101::14as35929.centraloregonix.org—Open
AS395378Cascade Divide Partners, LLC149.112.8.82001:504:101::8as395378.centraloregonix.org—Open
AS31748COIX149.112.8.1149.112.8.22001:504:101::12001:504:101::2rs1.centraloregonix.orgrs2.centraloregonix.org——Open
AS212232Port 179 LTD149.112.8.152001:504:101::15——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-12 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,167 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.