asn.dev

Observed topology

AS29066 VELIANET-AS velia.net Internetdienste GmbH

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29066: 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
AS34309Link11 GmbHUnclassifiedIPv4 IPv612,718
AS1299Arelion Sweden ABTransitIPv4 IPv68,549
AS174Cogent Communications, LLCTransitIPv4 IPv63,146
AS58453China Mobile International LimitedUnclassifiedIPv4 IPv6318

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50049RedSwitchesHostingIPv4353
AS199491South Communications Ltd.UnclassifiedIPv4 IPv689
AS35409TUCHA Sp. z o.o.UnclassifiedIPv459
AS136787PacketHub S.A.VPNIPv459
AS51833Association of IT Companies of KazakhstanHostingIPv4 IPv618
AS206768Association of IT Companies of KazakhstanHostingIPv4 IPv618

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS34309Link11 GmbHUnclassifiedIPv4 IPv612,767
AS1299Arelion Sweden ABTransitIPv4 IPv68,845
AS174Cogent Communications, LLCTransitIPv4 IPv63,340
AS58453China Mobile International LimitedUnclassifiedIPv4 IPv6375
AS50049RedSwitchesHostingIPv4353
AS199491South Communications Ltd.UnclassifiedIPv4 IPv689
AS35409TUCHA Sp. z o.o.UnclassifiedIPv459
AS136787PacketHub S.A.VPNIPv459
AS51833Association of IT Companies of KazakhstanHostingIPv4 IPv618
AS206768Association of IT Companies of KazakhstanHostingIPv4 IPv618

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.