asn.dev

Observed topology

AS65000 Use AS-

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS65000: 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
AS48541MTS PJSCUnclassifiedIPv414
AS17639Converge ICT Solutions Inc.UnclassifiedIPv410
AS27425IdeaTek Telcom, LLCResidentialIPv610
AS34038PJSC "Vimpelcom"UnclassifiedIPv46
AS56677Tele-Club Ltd.UnclassifiedIPv42
AS7795LUMOS Networks, Inc.HostingIPv41
AS33977Banat Telecom Satelit S.R.L.UnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS33977Banat Telecom Satelit S.R.L.UnclassifiedIPv43
AS14789Cloudflare, Inc.UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS48541MTS PJSCUnclassifiedIPv414
AS17639Converge ICT Solutions Inc.UnclassifiedIPv410
AS27425IdeaTek Telcom, LLCResidentialIPv610
AS33977Banat Telecom Satelit S.R.L.UnclassifiedIPv47
AS34038PJSC "Vimpelcom"UnclassifiedIPv46
AS56677Tele-Club Ltd.UnclassifiedIPv42
AS7795LUMOS Networks, Inc.HostingIPv41
AS8926Moldtelecom SAResidentialIPv41
AS14789Cloudflare, Inc.UnclassifiedIPv41

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.