Observed topology
AS16713 NOANET-WA - Northwest Open Access Network
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS16713: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
Transit
Downstream networks
Networks for which AS16713 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12086 | DT Micro, inc. | Unclassified | IPv4 | 4,319 |
| AS396872 | Advanced Internet | Unclassified | IPv4 IPv6 | 1,468 |
| AS13871 | Telebyte NW | Unclassified | IPv4 | 1,197 |
| AS23138 | FIRST STEP INTERNET, LLC | Residential | IPv4 IPv6 | 1,160 |
| AS22608 | Public Utility District No. 1 of Okanogan County | Unclassified | IPv4 IPv6 | 761 |
| AS7799 | Olypen, Inc. | Residential | IPv4 | 726 |
| AS395107 | RTI | Unclassified | IPv4 | 620 |
| AS20224 | Columbia Energy L.L.C | Unclassified | IPv4 IPv6 | 498 |
| AS27373 | Douglas County PUD | Unclassified | IPv4 IPv6 | 471 |
| AS397332 | City of Anacortes | Unclassified | IPv4 IPv6 | 349 |
Adjacency
Adjacent networks
Every AS seen directly next to AS16713 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 16,108 |
| AS12086 | DT Micro, inc. | Unclassified | IPv4 | 4,319 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 3,313 |
| AS23138 | FIRST STEP INTERNET, LLC | Residential | IPv4 IPv6 | 1,677 |
| AS396872 | Advanced Internet | Unclassified | IPv4 IPv6 | 1,468 |
| AS13871 | Telebyte NW | Unclassified | IPv4 | 1,197 |
| AS22608 | Public Utility District No. 1 of Okanogan County | Unclassified | IPv4 IPv6 | 1,093 |
| AS7799 | Olypen, Inc. | Residential | IPv4 | 726 |
| AS27373 | Douglas County PUD | Unclassified | IPv4 IPv6 | 680 |
| AS395107 | RTI | Unclassified | IPv4 | 620 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.