Observed topology
AS36012 HUNTER-COMM - HUNTER COMMUNICATIONS
Unclassified ARIN Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS36012: 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 AS36012 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS401911 | MAETRIX COMMUNICATIONS, LLC. | Unclassified | IPv4 IPv6 | 168 |
| AS21515 | SISKIYOU TELEPHONE COMPANY | Unclassified | IPv4 IPv6 | 114 |
| AS2726 | Webformix | Residential | IPv4 | 98 |
| AS13377 | Rogue Broadband | Unclassified | IPv4 IPv6 | 98 |
| AS401829 | Pipeworks Inc. | Unclassified | IPv4 IPv6 | 87 |
| AS32000 | Tnet Broadband Internet | Unclassified | IPv4 | 66 |
| AS18772 | Sky Lakes Medical Center, Inc. | Unclassified | IPv4 | 65 |
| AS14269 | Lifeline Computer Solutions, Inc. | Unclassified | IPv4 | 61 |
| AS398459 | Rogue Credit Union | Unclassified | IPv4 | 47 |
| AS32511 | Asante Health System | Unclassified | IPv4 | 39 |
Adjacency
Adjacent networks
Every AS seen directly next to AS36012 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,725 |
| AS21515 | SISKIYOU TELEPHONE COMPANY | Unclassified | IPv4 IPv6 | 178 |
| AS401911 | MAETRIX COMMUNICATIONS, LLC. | Unclassified | IPv4 IPv6 | 168 |
| AS2726 | Webformix | Residential | IPv4 | 98 |
| AS13377 | Rogue Broadband | Unclassified | IPv4 IPv6 | 98 |
| AS401829 | Pipeworks Inc. | Unclassified | IPv4 IPv6 | 87 |
| AS11404 | Wave Broadband | Residential | IPv4 | 84 |
| AS32000 | Tnet Broadband Internet | Unclassified | IPv4 | 66 |
| AS18772 | Sky Lakes Medical Center, Inc. | Unclassified | IPv4 | 65 |
| AS14269 | Lifeline Computer Solutions, Inc. | Unclassified | IPv4 | 61 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.