Observed topology

AS30936 RENET-COM-AS RENET COM Autonomous System

Unclassified RIPE

Upstreams 2 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS30936: 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
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	131
AS31133	PJSC MegaFon	Mobile	IPv4	73

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS51051	Administration department of the Government of Saratov region	Unclassified	IPv4	60
AS202344	LLC Basalt Svobodnoe Programnoe Obespechenie	Unclassified	IPv4	60
AS21375	JSC "Concern Rosenergoatom"	Unclassified	IPv4	39
AS48143	"M-Tekhnologii" Ltd	Unclassified	IPv4	6
AS209962	PJSC Rosseti Volga	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	231
AS31133	PJSC MegaFon	Mobile	IPv4	139
AS51051	Administration department of the Government of Saratov region	Unclassified	IPv4	60
AS202344	LLC Basalt Svobodnoe Programnoe Obespechenie	Unclassified	IPv4	60
AS21375	JSC "Concern Rosenergoatom"	Unclassified	IPv4	39
AS48143	"M-Tekhnologii" Ltd	Unclassified	IPv4	6
AS209962	PJSC Rosseti Volga	Unclassified	IPv4	1

Provenance

Where this comes from

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