asn.dev

Observed topology

AS211041 SWOOTH-AS

Residential RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS211041: 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
AS35133Eranium B.V.HostingIPv4 IPv6114
AS44103The Mastermind Holding B.V.UnclassifiedIPv4 IPv681
AS6939Hurricane Electric LLCTransitIPv424
AS50304Blix Solutions ASUnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv65
AS58057Securebit AGUnclassifiedIPv4 IPv65
AS1103SURF B.V.UnclassifiedIPv4 IPv64
AS34019Hivane AssociationUnclassifiedIPv4 IPv63
AS202365Omer GOLGELIUnclassifiedIPv43
AS20764CJSC RASCOMUnclassifiedIPv42

All 13 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS35133Eranium B.V.HostingIPv4 IPv6114
AS44103The Mastermind Holding B.V.UnclassifiedIPv4 IPv681
AS6939Hurricane Electric LLCTransitIPv424
AS50304Blix Solutions ASUnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv65
AS58057Securebit AGUnclassifiedIPv4 IPv65
AS1103SURF B.V.UnclassifiedIPv4 IPv64
AS34019Hivane AssociationUnclassifiedIPv4 IPv63
AS202365Omer GOLGELIUnclassifiedIPv43
AS20764CJSC RASCOMUnclassifiedIPv42

All 13 adjacent →

Provenance

Where this comes from

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