asn.dev

Observed topology

AS43740 ZTK-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43740: 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
AS12389PJSC RostelecomResidentialIPv4276
AS3216PJSC "Vimpelcom"MobileIPv4138
AS59692IQWeb FZ-LLCUnclassifiedIPv457
AS8359MTS PJSCMobileIPv453
AS29226JSC MastertelUnclassifiedIPv414
AS35401AO "Tele-Service Tula"UnclassifiedIPv46
AS57724DDOS-GUARD LTDUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS65102unnamedUnclassifiedIPv48

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4284
AS3216PJSC "Vimpelcom"MobileIPv4138
AS59692IQWeb FZ-LLCUnclassifiedIPv457
AS8359MTS PJSCMobileIPv453
AS29226JSC MastertelUnclassifiedIPv414
AS65102unnamedUnclassifiedIPv48
AS35401AO "Tele-Service Tula"UnclassifiedIPv46
AS57724DDOS-GUARD LTDUnclassifiedIPv42

Provenance

Where this comes from

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