Observed topology

AS60245 NET-23NET-AS Sannikov Kirill Vladimirovich

Unclassified APNIC

Upstreams 7 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60245: 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	304
AS61031	ESCOMTEL BACKGROUND COMMUNICATION NETWORKS Ltd.	Residential	IPv4	88
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	73
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	46
AS51028	Zummer LLC	Unclassified	IPv4	39
AS50673	Serverius Holding B.V.	Unclassified	IPv4	4
AS208972	GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI	Unclassified	IPv4	4

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12389	PJSC Rostelecom	Residential	IPv4	304
AS61031	ESCOMTEL BACKGROUND COMMUNICATION NETWORKS Ltd.	Residential	IPv4	88
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	73
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	46
AS51028	Zummer LLC	Unclassified	IPv4	39
AS50673	Serverius Holding B.V.	Unclassified	IPv4	4
AS208972	GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI	Unclassified	IPv4	4

Provenance

Where this comes from

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