asn.dev

Observed topology

AS24611 DCLUX-AS Datacenter Luxembourg

Hosting RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS24611: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6385
AS55002F5, Inc.UnclassifiedIPv4224
AS6661POST LuxembourgResidentialIPv4 IPv6210
AS6939Hurricane Electric LLCTransitIPv460
AS33891Core-Backbone GmbHHostingIPv416
AS24482SG.GSHostingIPv4 IPv613
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv613
AS20766Association "Gitoyen"UnclassifiedIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv412
AS45049Mohamed El BoudduntiResidentialIPv4 IPv611

All 17 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206504RCARRE S.A.UnclassifiedIPv455
AS208414WEDOS Internet, a.s.HostingIPv634
AS43719Kyndryl Luxembourg SarlUnclassifiedIPv65

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6404
AS6661POST LuxembourgResidentialIPv4 IPv6254
AS55002F5, Inc.UnclassifiedIPv4224
AS6939Hurricane Electric LLCTransitIPv4 IPv674
AS206504RCARRE S.A.UnclassifiedIPv455
AS208414WEDOS Internet, a.s.HostingIPv634
AS33891Core-Backbone GmbHHostingIPv416
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv616
AS24482SG.GSHostingIPv4 IPv615
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv614

All 22 adjacent →

Provenance

Where this comes from

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