asn.dev

Observed topology

AS59780 SURFBOXX Surfboxx IT-Solutions GmbH

Unclassified RIPE Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59780: 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
AS33891Core-Backbone GmbHHostingIPv4 IPv6246
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6154
AS6939Hurricane Electric LLCTransitIPv610
AS24482SG.GSHostingIPv4 IPv67
AS6797GlobalConnect ABUnclassifiedIPv46
AS8218Zayo Infrastructure France SAUnclassifiedIPv46
AS20562Broadband Hosting B.V.HostingIPv46
AS24961WIIT AGHostingIPv46
AS50629LWLcom GmbHUnclassifiedIPv46

Transit

Downstream networks

inferred

Networks for which AS59780 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS33891Core-Backbone GmbHHostingIPv4 IPv6246
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6154
AS6939Hurricane Electric LLCTransitIPv610
AS24482SG.GSHostingIPv4 IPv67
AS6797GlobalConnect ABUnclassifiedIPv46
AS8218Zayo Infrastructure France SAUnclassifiedIPv46
AS20562Broadband Hosting B.V.HostingIPv46
AS24961WIIT AGHostingIPv46
AS50629LWLcom GmbHUnclassifiedIPv46

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.