asn.dev

Observed topology

AS41344 VOL-AS

Unclassified RIPE

Upstreams 6 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 2
Upstream graph Who carries AS41344, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS41344 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS41344: 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
AS43727JSC KVANT-TELEKOMResidentialIPv4361
AS12389PJSC RostelecomResidentialIPv4342
AS31133PJSC MegaFonMobileIPv490
AS24482SG.GSHostingIPv4 IPv614
AS37721Virtual Technologies & SolutionsResidentialIPv413
AS25091IP-Max SAUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39442JSC RDE "Unico"UnclassifiedIPv42,256
AS51032LLC POWERNETResidentialIPv456

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS39442JSC RDE "Unico"UnclassifiedIPv42,283
AS43727JSC KVANT-TELEKOMResidentialIPv41,397
AS12389PJSC RostelecomResidentialIPv41,341
AS31133PJSC MegaFonMobileIPv4291
AS51032LLC POWERNETResidentialIPv456
AS24482SG.GSHostingIPv4 IPv651
AS37721Virtual Technologies & SolutionsResidentialIPv450
AS6939Hurricane Electric LLCTransitIPv428
AS25091IP-Max SAUnclassifiedIPv62
AS34927iFog GmbHHostingIPv41

Provenance

Where this comes from

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