Observed topology
AS395466 GLOBALNET - Global Net
Residential APNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS395466: 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 |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 82 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 65 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 39 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 4 |
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 4 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 3 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 | 3 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 3 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 2 |
| AS293 | ESnet | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS395466 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS32146 | City of Bozeman | Unclassified | IPv4 | 38 |
Adjacency
Adjacent networks
Every AS seen directly next to AS395466 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 100 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 72 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 46 |
| AS32146 | City of Bozeman | Unclassified | IPv4 | 38 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 5 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 4 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 | 4 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 4 |
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 4 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 3 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-06 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.