asn.dev

Observed topology

AS210834 LU-CIX-IT LU-CIX Management G.I.E.

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS210834: 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
AS56665Proximus Luxembourg S.A.ResidentialIPv4 IPv6531
AS208374LU-CIX Management G.I.E.UnclassifiedIPv4 IPv677
AS6939Hurricane Electric LLCTransitIPv462
AS24482SG.GSHostingIPv4 IPv615
AS34019Hivane AssociationUnclassifiedIPv4 IPv615
AS45049Mohamed El BoudduntiResidentialIPv4 IPv611
AS48185team.blue NVUnclassifiedIPv4 IPv611
AS29632Netassist International EOODUnclassifiedIPv67
AS60497Uwe ZeidlerHostingIPv44
AS6696VERIXI SAUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS20940Akamai International B.V.HostingIPv4 IPv681
AS63293Facebook, Inc.HostingIPv4 IPv657

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS56665Proximus Luxembourg S.A.ResidentialIPv4 IPv6573
AS208374LU-CIX Management G.I.E.UnclassifiedIPv4 IPv6173
AS20940Akamai International B.V.HostingIPv4 IPv681
AS6939Hurricane Electric LLCTransitIPv462
AS63293Facebook, Inc.HostingIPv4 IPv657
AS24482SG.GSHostingIPv4 IPv615
AS34019Hivane AssociationUnclassifiedIPv4 IPv615
AS45049Mohamed El BoudduntiResidentialIPv4 IPv611
AS48185team.blue NVUnclassifiedIPv4 IPv611
AS29632Netassist International EOODUnclassifiedIPv67

All 12 adjacent →

Provenance

Where this comes from

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