asn.dev

Observed topology

AS208374 LU-CIX Management G.I.E.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS208374: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202438Encevo S.AUnclassifiedIPv4215
AS210834LU-CIX Management G.I.E.HostingIPv4 IPv679

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS202438Encevo S.AUnclassifiedIPv4215
AS210834LU-CIX Management G.I.E.HostingIPv4 IPv6175
AS9002RETN LimitedUnclassifiedIPv4 IPv6174
AS1299Arelion Sweden ABTransitIPv4 IPv6173
AS3257GTT Communications Inc.TransitIPv4 IPv627
AS6696VERIXI SAUnclassifiedIPv45
AS24482SG.GSHostingIPv45
AS34019Hivane AssociationUnclassifiedIPv45
AS5511Orange S.A.TransitIPv41

Provenance

Where this comes from

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