Observed topology
AS36416 CLACKESD - Clackamas Education Service District
Unclassified ARIN Educational/Research
Transit
Upstream networks
Networks observed carrying traffic for AS36416: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20055 | Wholesail networks LLC | Residential | IPv4 IPv6 | 192 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 74 |
| AS3701 | University of Oregon | Education | IPv4 IPv6 | 52 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 10 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 6 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 6 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 5 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 5 |
Transit
Downstream networks
Networks for which AS36416 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS36416 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20055 | Wholesail networks LLC | Residential | IPv4 IPv6 | 643 |
| AS3933 | Oregon Public Education Network | Education | IPv4 | 562 |
| AS3701 | University of Oregon | Education | IPv4 IPv6 | 202 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 199 |
| AS18995 | Clackamas County | Unclassified | IPv4 IPv6 | 111 |
| AS20469 | Tri-County Metropolitan Transit District | Unclassified | IPv4 | 63 |
| AS32365 | City of Sandy | Unclassified | IPv4 IPv6 | 42 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 34 |
| AS23038 | City of Hillsboro | Unclassified | IPv4 | 24 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 19 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-02 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.44M 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.