asn.dev

Observed topology

AS41034 IMPULS-AS Ltd. "SPA"Impulse"

Unclassified RIPE

Upstreams 4 carry this network
Downstreams 8 this network carries
Adjacent (IPv4) 13
Adjacent (IPv6) 3
Upstream graph Who carries AS41034, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS41034 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS41034: 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 RostelecomResidentialIPv4 IPv62,098
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6905
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv6673
AS8359MTS PJSCMobileIPv432

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS13296INNOR Ltd.UnclassifiedIPv4330
AS198774Ltd. "Regional Media Transit"UnclassifiedIPv4258
AS202058Ekaterinburg-2000 LLCUnclassifiedIPv4248
AS212800Cocobri, OOOUnclassifiedIPv466
AS42899Internet Plus LLCUnclassifiedIPv463
AS201231Nemcev Vitaliy Nikolaevich PEUnclassifiedIPv462
AS58155Web Depo LtdUnclassifiedIPv461
AS61382Komisvyazinvest LLCUnclassifiedIPv450

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv63,142
AS3216PJSC "Vimpelcom"MobileIPv4 IPv61,072
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv6724
AS13296INNOR Ltd.UnclassifiedIPv4330
AS198774Ltd. "Regional Media Transit"UnclassifiedIPv4258
AS202058Ekaterinburg-2000 LLCUnclassifiedIPv4248
AS31656EmNet LtdUnclassifiedIPv4112
AS61382Komisvyazinvest LLCUnclassifiedIPv476
AS212800Cocobri, OOOUnclassifiedIPv466
AS42899Internet Plus LLCUnclassifiedIPv463

All 13 adjacent →

Provenance

Where this comes from

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