asn.dev

Observed topology

AS58065 PACKETEXCHANGE

Unclassified APNIC

Upstreams 9 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 5
Upstream graph Who carries AS58065, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS58065 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58065: 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.

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv614,999
AS6939Hurricane Electric LLCTransitIPv4 IPv62,070
AS41564Orion Network LimitedHostingIPv41,914
AS1299Arelion Sweden ABTransitIPv4 IPv61,387
AS209378Inios OyUnclassifiedIPv4 IPv61,332
AS51269HEXATOM s.a.r.l.UnclassifiedIPv4812
AS395584Data ManagementUnclassifiedIPv4660
AS18229CtrlSHostingIPv4 IPv6155
AS24482SG.GSHostingIPv43

Transit

Downstream networks

inferred

Networks for which AS58065 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS41564Orion Network LimitedHostingIPv43,283

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS58065 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv616,918
AS41564Orion Network LimitedHostingIPv45,197
AS6939Hurricane Electric LLCTransitIPv4 IPv62,488
AS1299Arelion Sweden ABTransitIPv4 IPv61,387
AS209378Inios OyUnclassifiedIPv4 IPv61,332
AS133296Web Werks India Pvt. Ltd.ResidentialIPv4904
AS51269HEXATOM s.a.r.l.UnclassifiedIPv4812
AS395584Data ManagementUnclassifiedIPv4660
AS18229CtrlSHostingIPv4 IPv6155
AS24482SG.GSHostingIPv445

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-19 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.