asn.dev

Observed topology

AS65021

Unclassified ARIN

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS40663IncogNet LLCVPNIPv4 IPv64
AS135392MillenialHost LimitedUnclassifiedIPv42
AS200461Ian David KlemmUnclassifiedIPv4 IPv62
AS216382LAYER MARKETING SERVICES L.L.CUnclassifiedIPv4 IPv62
AS398906Conviction HQUnclassifiedIPv42
AS401619HostBilby Inc.HostingIPv4 IPv62

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS400304Redoubt NetworksHostingIPv4 IPv614
AS40663IncogNet LLCVPNIPv4 IPv64
AS135392MillenialHost LimitedUnclassifiedIPv42
AS200461Ian David KlemmUnclassifiedIPv4 IPv62
AS216382LAYER MARKETING SERVICES L.L.CUnclassifiedIPv4 IPv62
AS398906Conviction HQUnclassifiedIPv42
AS401619HostBilby Inc.HostingIPv4 IPv62

Provenance

Where this comes from

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