asn.dev

Observed topology

AS35052 AS_AT_TLD_SERVICES Vienna University

Unclassified RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS35052: 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
AS1921ipcom GmbHHostingIPv4 IPv650
AS553Universitaet StuttgartUnclassifiedIPv4 IPv644
AS8674Netnod ABUnclassifiedIPv4 IPv628
AS31529DENIC eGUnclassifiedIPv4 IPv619
AS1853ACONETUnclassifiedIPv4 IPv616
AS8763DENIC eGUnclassifiedIPv4 IPv612
AS6881NIX.CZ z.s.p.o.UnclassifiedIPv4 IPv69
AS20473The Constant Company, LLCHostingIPv4 IPv67
AS42473Anexia Cloud Solutions GmbHHostingIPv4 IPv67
AS22548Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv4 IPv63

All 13 upstreams →

Transit

Downstream networks

inferred

Networks for which AS35052 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 AS35052 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS1921ipcom GmbHHostingIPv4 IPv650
AS553Universitaet StuttgartUnclassifiedIPv4 IPv644
AS8674Netnod ABUnclassifiedIPv4 IPv628
AS31529DENIC eGUnclassifiedIPv4 IPv619
AS1853ACONETUnclassifiedIPv4 IPv616
AS8763DENIC eGUnclassifiedIPv4 IPv612
AS6881NIX.CZ z.s.p.o.UnclassifiedIPv4 IPv69
AS20473The Constant Company, LLCHostingIPv4 IPv67
AS42473Anexia Cloud Solutions GmbHHostingIPv4 IPv67
AS22548Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv4 IPv63

All 13 adjacent →

Provenance

Where this comes from

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