asn.dev

Observed topology

AS39063 LEITWERT Leitwert GmbH

Unclassified RIPE Educational/Research

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

Transit

Upstream networks

All 28

Networks observed carrying traffic for AS39063: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6220
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv648
AS1299Arelion Sweden ABTransitIPv4 IPv626
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv616
AS3356Level 3 Parent, LLCTransitIPv4 IPv614
AS1836green.ch AGResidentialIPv4 IPv612
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv612
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv612
AS48185team.blue NVUnclassifiedIPv4 IPv612

All 28 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS29108Leitwert GmbHUnclassifiedIPv4 IPv61,655

Adjacency

Adjacent networks

All 59

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

ASNetworkTypeFamiliesPaths seen
AS29108Leitwert GmbHUnclassifiedIPv4 IPv61,655
AS6939Hurricane Electric LLCTransitIPv4 IPv6524
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv6141
AS3320Deutsche Telekom AGMobileIPv4 IPv6128
AS1299Arelion Sweden ABTransitIPv4 IPv6117
AS3356Level 3 Parent, LLCTransitIPv4 IPv6108
AS2914NTT America, Inc.TransitIPv4 IPv697
AS12389PJSC RostelecomResidentialIPv4 IPv697
AS174Cogent Communications, LLCTransitIPv4 IPv694
AS23764CTGNetUnclassifiedIPv4 IPv694

All 59 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.