Observed topology

AS42038 VLADLINK-AS Krivets Sergey Sergeevich

Unclassified RIPE

Upstreams 8 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42038: 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	310
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	188
AS8359	MTS PJSC	Mobile	IPv4	62
AS31133	PJSC MegaFon	Mobile	IPv4	60
AS43298	Storm Networks LLC	Unclassified	IPv4	35
AS59796	StormWall s.r.o.	Unclassified	IPv4	26
AS25091	IP-Max SA	Unclassified	IPv4	22
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	20

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS47636	Nitsora Alena Vladimirovna	Unclassified	IPv4	65

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12389	PJSC Rostelecom	Residential	IPv4	338
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	201
AS31133	PJSC MegaFon	Mobile	IPv4	74
AS8359	MTS PJSC	Mobile	IPv4	66
AS47636	Nitsora Alena Vladimirovna	Unclassified	IPv4	65
AS43298	Storm Networks LLC	Unclassified	IPv4	35
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	26
AS59796	StormWall s.r.o.	Unclassified	IPv4	26
AS25091	IP-Max SA	Unclassified	IPv4	22

Provenance

Where this comes from

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