asn.dev

Observed topology

AS42065 ETELECOM-AS Global Network Management Inc

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42065: 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
AS31500Global Network Management IncUnclassifiedIPv4 IPv61,306
AS6939Hurricane Electric LLCTransitIPv4341
AS8447A1 Telekom Austria AGResidentialIPv431
AS24482SG.GSHostingIPv431
AS33891Core-Backbone GmbHHostingIPv431
AS37721Virtual Technologies & SolutionsResidentialIPv431
AS49673Truenetwork LLCUnclassifiedIPv431
AS50673Serverius Holding B.V.UnclassifiedIPv431
AS56655Gigahost ASUnclassifiedIPv431
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv431

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57629LLC IVI.RUHostingIPv632

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS31500Global Network Management IncUnclassifiedIPv4 IPv61,325
AS6939Hurricane Electric LLCTransitIPv4 IPv6353
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv632
AS57629LLC IVI.RUHostingIPv632
AS8447A1 Telekom Austria AGResidentialIPv431
AS24482SG.GSHostingIPv431
AS33891Core-Backbone GmbHHostingIPv431
AS49673Truenetwork LLCUnclassifiedIPv431
AS50673Serverius Holding B.V.UnclassifiedIPv431
AS56655Gigahost ASUnclassifiedIPv431

All 11 adjacent →

Provenance

Where this comes from

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