asn.dev

Observed topology

AS60345 IXNET ixnt

Unclassified RIPE

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS60345: 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
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6142
AS1299Arelion Sweden ABTransitIPv4 IPv689
AS6204INTERKVM HOST SRLUnclassifiedIPv476
AS6939Hurricane Electric LLCTransitIPv4 IPv673
AS50304Blix Solutions ASUnclassifiedIPv410
AS24482SG.GSHostingIPv4 IPv68
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv68
AS212024Marc SchmittUnclassifiedIPv4 IPv68
AS1836green.ch AGResidentialIPv47
AS37721Virtual-Technologies-Solutions-SAResidentialIPv47

All 18 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44803Webdock.io ApSUnclassifiedIPv42,635
AS199771Stadtwerke Weinheim GmbHUnclassifiedIPv460

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS44803Webdock.io ApSUnclassifiedIPv42,635
AS50629LWLcom GmbHUnclassifiedIPv4 IPv61,089
AS1299Arelion Sweden ABTransitIPv4 IPv6678
AS6204INTERKVM HOST SRLUnclassifiedIPv4519
AS6939Hurricane Electric LLCTransitIPv4 IPv6377
AS50304Blix Solutions ASUnclassifiedIPv4106
AS199771Stadtwerke Weinheim GmbHUnclassifiedIPv460
AS24482SG.GSHostingIPv4 IPv656
AS1836green.ch AGResidentialIPv455
AS37721Virtual-Technologies-Solutions-SAResidentialIPv455

All 23 adjacent →

Provenance

Where this comes from

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