Observed topology
AS7782 ALSK-7782 - Alaska Communications Systems Group, Inc.
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS7782: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,234 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 422 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 28 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 28 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 26 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 26 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 26 |
Transit
Downstream networks
Networks for which AS7782 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS396006 | SPITwSPOTS | Unclassified | IPv4 | 1,891 |
| AS46932 | Anchorage School District | Unclassified | IPv4 | 594 |
| AS15269 | ConocoPhillips Company | Unclassified | IPv4 | 512 |
| AS3724 | State of Alaska | Unclassified | IPv4 | 405 |
| AS395475 | SnowCloud Services LLC | Unclassified | IPv4 IPv6 | 402 |
| AS393276 | Chugach Electric Association, Inc. | Unclassified | IPv4 | 396 |
| AS53942 | Cordova Telecom Cooperative, Incorporated | Unclassified | IPv4 IPv6 | 292 |
| AS19127 | Heritage NetWorks, LLC | Unclassified | IPv4 IPv6 | 202 |
| AS397824 | Alaska Permanent Fund Corporation, an instrumentality of the State of Alaska | Unclassified | IPv4 IPv6 | 191 |
| AS20259 | Copper Valley Long Distance, LLC | Unclassified | IPv4 IPv6 | 145 |
Adjacency
Adjacent networks
Every AS seen directly next to AS7782 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 6,138 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 2,776 |
| AS396006 | SPITwSPOTS | Unclassified | IPv4 | 1,891 |
| AS19127 | Heritage NetWorks, LLC | Unclassified | IPv4 IPv6 | 613 |
| AS46932 | Anchorage School District | Unclassified | IPv4 | 594 |
| AS15269 | ConocoPhillips Company | Unclassified | IPv4 | 512 |
| AS20259 | Copper Valley Long Distance, LLC | Unclassified | IPv4 IPv6 | 411 |
| AS3724 | State of Alaska | Unclassified | IPv4 | 405 |
| AS395475 | SnowCloud Services LLC | Unclassified | IPv4 IPv6 | 402 |
| AS393276 | Chugach Electric Association, Inc. | Unclassified | IPv4 | 396 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-03 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.45M 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.