Observed topology

AS60651 STEK-KAZAN from Rostelecom

Unclassified RIPE

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 2

Upstream graph Who carries AS60651, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS60651 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60651: 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.

AS	Network	Type	Families	Paths seen
AS12389	PJSC Rostelecom	Residential	IPv4 IPv6	605
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4 IPv6	237
AS62067	Telecom Service LLC	Unclassified	IPv4	13

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS56692	KBER Bank Kazani limited liability company	Unclassified	IPv4	63
AS62150	BARS Group JSC	Unclassified	IPv4	63
AS214612	JSC National NPF	Unclassified	IPv4	63

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12389	PJSC Rostelecom	Residential	IPv4 IPv6	740
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4 IPv6	288
AS56692	KBER Bank Kazani limited liability company	Unclassified	IPv4	63
AS62150	BARS Group JSC	Unclassified	IPv4	63
AS214612	JSC National NPF	Unclassified	IPv4	63
AS62067	Telecom Service LLC	Unclassified	IPv4	16

Provenance

Where this comes from

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