asn.dev

Observed topology

AS43045 SvHold-AS Svyaz-Holding Ltd.

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43045: 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
AS20764CJSC RASCOMUnclassifiedIPv4 IPv670
AS3216PJSC "Vimpelcom"MobileIPv4 IPv667
AS47122CYBERFIRST LLCUnclassifiedIPv463
AS57724DDOS-GUARD LTDUnclassifiedIPv460
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv634
AS31133PJSC MegaFonMobileIPv4 IPv634
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS49673Truenetwork LLCUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204952JSC "ER-Telecom Holding"UnclassifiedIPv440
AS31690GeoTelecommunications LLCUnclassifiedIPv436

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS57724DDOS-GUARD LTDUnclassifiedIPv4100
AS20764CJSC RASCOMUnclassifiedIPv4 IPv685
AS3216PJSC "Vimpelcom"MobileIPv4 IPv672
AS47122CYBERFIRST LLCUnclassifiedIPv463
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv648
AS204952JSC "ER-Telecom Holding"UnclassifiedIPv440
AS31690GeoTelecommunications LLCUnclassifiedIPv436
AS31133PJSC MegaFonMobileIPv4 IPv634
AS49673Truenetwork LLCUnclassifiedIPv45
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv65

All 12 adjacent →

Provenance

Where this comes from

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