asn.dev

Observed topology

AS60771 C-CORP-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60771: 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
AS29076Citytelecom LLCHostingIPv4531
AS3216PJSC "Vimpelcom"MobileIPv4112
AS47656Ast-Systems Ltd.UnclassifiedIPv453
AS8595OOO WestCall Ltd.UnclassifiedIPv443
AS31200Novotelecom LtdUnclassifiedIPv440
AS8359MTS PJSCMobileIPv427
AS60840OJSC Telecom-ServiceUnclassifiedIPv424
AS24482SG.GSHostingIPv49
AS37721Virtual Technologies & SolutionsResidentialIPv49
AS24955JSC "Ufanet"ResidentialIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211616JSC RZD-ZdorovieUnclassifiedIPv461

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS29076Citytelecom LLCHostingIPv4595
AS3216PJSC "Vimpelcom"MobileIPv4112
AS211616JSC RZD-ZdorovieUnclassifiedIPv461
AS47656Ast-Systems Ltd.UnclassifiedIPv453
AS8595OOO WestCall Ltd.UnclassifiedIPv443
AS31200Novotelecom LtdUnclassifiedIPv440
AS8359MTS PJSCMobileIPv427
AS60840OJSC Telecom-ServiceUnclassifiedIPv424
AS24482SG.GSHostingIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410

Provenance

Where this comes from

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