asn.dev

Observed topology

AS41560 UT-SVR

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 17

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 RASCOMUnclassifiedIPv41,247
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4646
AS1299Arelion Sweden ABTransitIPv4531
AS12722RECONN LLCHostingIPv4309
AS3216PJSC "Vimpelcom"MobileIPv4227
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4117
AS31133PJSC MegaFonMobileIPv484
AS25478iHome LLCUnclassifiedIPv457
AS50673Serverius Holding B.V.UnclassifiedIPv443
AS24482SG.GSHostingIPv435

All 17 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 LLCUnclassifiedIPv4497
AS203493Egor TimoshenkoHostingIPv42

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS20764CJSC RASCOMUnclassifiedIPv41,471
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4734
AS1299Arelion Sweden ABTransitIPv4627
AS56542UGMK-Telecom LLCUnclassifiedIPv4497
AS12722RECONN LLCHostingIPv4309
AS3216PJSC "Vimpelcom"MobileIPv4267
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4128
AS31133PJSC MegaFonMobileIPv484
AS25478iHome LLCUnclassifiedIPv457
AS50673Serverius Holding B.V.UnclassifiedIPv451

All 19 adjacent →

Provenance

Where this comes from

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