asn.dev

Observed topology

AS39045 GAZTELECOM-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39045: 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 RostelecomResidentialIPv4 IPv61,853
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4479
AS31133PJSC MegaFonMobileIPv4224
AS3216PJSC "Vimpelcom"MobileIPv457
AS24482SG.GSHostingIPv4 IPv613
AS49673Truenetwork LLCUnclassifiedIPv412
AS25091IP-Max SAUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50703Federal State Budgetary Institution of Science Federal Research Center "Geophysical Survey of the Russian Academy of Sciences"UnclassifiedIPv442
AS203353Agrisovgaz Ltd.UnclassifiedIPv417
AS21166SatGate LLCUnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv61,900
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4495
AS31133PJSC MegaFonMobileIPv4224
AS3216PJSC "Vimpelcom"MobileIPv457
AS50703Federal State Budgetary Institution of Science Federal Research Center "Geophysical Survey of the Russian Academy of Sciences"UnclassifiedIPv442
AS203353Agrisovgaz Ltd.UnclassifiedIPv417
AS24482SG.GSHostingIPv4 IPv613
AS49673Truenetwork LLCUnclassifiedIPv412
AS21166SatGate LLCUnclassifiedIPv44
AS25091IP-Max SAUnclassifiedIPv61

Provenance

Where this comes from

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