asn.dev

Observed topology

AS52341 AS52341 - WOM SpA

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52341: 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
AS263237PowerHost Telecom SPAUnclassifiedIPv4 IPv62,105
AS3356Level 3 Parent, LLCTransitIPv41,743
AS174Cogent Communications, LLCTransitIPv4 IPv6366
AS6939Hurricane Electric LLCTransitIPv4 IPv6150

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv699
AS54994Meteverse Limited.UnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263237PowerHost Telecom SPAUnclassifiedIPv4 IPv62,233
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,779
AS174Cogent Communications, LLCTransitIPv4 IPv6366
AS6939Hurricane Electric LLCTransitIPv4 IPv6150
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv699
AS54994Meteverse Limited.UnclassifiedIPv465

Provenance

Where this comes from

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