Observed topology

AS13105 LUKOIL-INFORM-AS

Unclassified RIPE

Upstreams 12 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 12

Adjacent (IPv6) 0

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS13105: 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	476
AS12389	PJSC Rostelecom	Residential	IPv4	444
AS8359	MTS PJSC	Mobile	IPv4	114
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	63
AS34875	PJSC Rostelecom	Unclassified	IPv4	62
AS21191	Joint Stock Company TransTeleCom	Unclassified	IPv4	59
AS5610	O2 Czech Republic, a.s.	Unclassified	IPv4	58
AS57304	JSC "RetnNet"	Unclassified	IPv4	31
AS56534	Comfortel Ltd.	Unclassified	IPv4	28
AS28812	PJSC "Bashinformsvyaz"	Unclassified	IPv4	25

All 12 upstreams →

Transit

Downstream networks

inferred

Networks for which AS13105 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

All 12

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

AS	Network	Type	Families	Paths seen
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	476
AS12389	PJSC Rostelecom	Residential	IPv4	444
AS8359	MTS PJSC	Mobile	IPv4	114
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	63
AS34875	PJSC Rostelecom	Unclassified	IPv4	62
AS21191	Joint Stock Company TransTeleCom	Unclassified	IPv4	59
AS5610	O2 Czech Republic, a.s.	Unclassified	IPv4	58
AS57304	JSC "RetnNet"	Unclassified	IPv4	31
AS56534	Comfortel Ltd.	Unclassified	IPv4	28
AS28812	PJSC "Bashinformsvyaz"	Unclassified	IPv4	25

All 12 adjacent →

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.