asn.dev

Observed topology

AS41560 UT-SVR UGMK-Telecom LLC

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS41560: 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 RASCOMUnclassifiedIPv4645
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4626
AS25478iHome LLCUnclassifiedIPv4594
AS1299Arelion Sweden ABTransitIPv4567
AS12722RECONN LLCHostingIPv4309
AS3216PJSC "Vimpelcom"MobileIPv4234
AS31133PJSC MegaFonMobileIPv4120
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv487
AS50673Serverius Holding B.V.UnclassifiedIPv443
AS50384iHome LLCUnclassifiedIPv442

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS56542UGMK-Telecom LLCUnclassifiedIPv4500

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS20764CJSC RASCOMUnclassifiedIPv4741
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4734
AS25478iHome LLCUnclassifiedIPv4698
AS1299Arelion Sweden ABTransitIPv4671
AS56542UGMK-Telecom LLCUnclassifiedIPv4500
AS12722RECONN LLCHostingIPv4309
AS3216PJSC "Vimpelcom"MobileIPv4274
AS31133PJSC MegaFonMobileIPv4120
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv487
AS50673Serverius Holding B.V.UnclassifiedIPv451

All 20 adjacent →

Provenance

Where this comes from

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