asn.dev

Observed topology

AS38917 komtel-as INTERCOMTEL Limited Company

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.

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4480
AS31133PJSC MegaFonMobileIPv4385
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6268
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4222

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198541INTERCOMTEL Limited CompanyUnclassifiedIPv4441
AS42393Svyaz-Kontrakt LLCUnclassifiedIPv4126
AS51730OOO IT-TcentrUnclassifiedIPv463
AS29114Limited Liability Company "Business information technology"UnclassifiedIPv448
AS51781Gazprom Megregiongaz Ivanovo LLCUnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4739
AS31133PJSC MegaFonMobileIPv4579
AS198541INTERCOMTEL Limited CompanyUnclassifiedIPv4504
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4404
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6397
AS42393Svyaz-Kontrakt LLCUnclassifiedIPv4126
AS29114Limited Liability Company "Business information technology"UnclassifiedIPv467
AS51730OOO IT-TcentrUnclassifiedIPv463
AS51781Gazprom Megregiongaz Ivanovo LLCUnclassifiedIPv44

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.