Observed topology

AS38917 KOMTEL-AS

Unclassified RIPE

Upstreams 4 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38917: 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	481
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	342
AS3216	PJSC "Vimpelcom"	Mobile	IPv4 IPv6	265
AS31133	PJSC MegaFon	Mobile	IPv4	245

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS198541	INTERCOMTEL Limited Company	Unclassified	IPv4	434
AS42393	Svyaz-Kontrakt LLC	Unclassified	IPv4	124
AS51730	OOO IT-Tcentr	Unclassified	IPv4	62
AS29114	Limited Liability Company "Business information technology"	Unclassified	IPv4	47
AS51781	Gazprom Megregiongaz Ivanovo LLC	Unclassified	IPv4	3

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12389	PJSC Rostelecom	Residential	IPv4	749
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	509
AS198541	INTERCOMTEL Limited Company	Unclassified	IPv4	496
AS3216	PJSC "Vimpelcom"	Mobile	IPv4 IPv6	414
AS31133	PJSC MegaFon	Mobile	IPv4	413
AS42393	Svyaz-Kontrakt LLC	Unclassified	IPv4	124
AS29114	Limited Liability Company "Business information technology"	Unclassified	IPv4	67
AS51730	OOO IT-Tcentr	Unclassified	IPv4	62
AS51781	Gazprom Megregiongaz Ivanovo LLC	Unclassified	IPv4	3

Provenance

Where this comes from

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