asn.dev

Observed topology

AS59570 HOSTINGSTUDIO

Hosting RIPE

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

Transit

Upstream networks

All 24

Networks observed carrying traffic for AS59570: 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 IPv683
AS34927iFog GmbHHostingIPv4 IPv630
AS58057Securebit AGUnclassifiedIPv4 IPv611
AS29632Netassist International EOODUnclassifiedIPv66
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv65
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv64
AS357084b42 UGUnclassifiedIPv4 IPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS56755Securebit AGUnclassifiedIPv4 IPv64

All 24 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208454Jens ZimperfeldHostingIPv637
AS112DNS-OARCUnclassifiedIPv4 IPv66

Adjacency

Adjacent networks

All 27

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6111
AS208454Jens ZimperfeldHostingIPv637
AS34927iFog GmbHHostingIPv4 IPv630
AS58057Securebit AGUnclassifiedIPv4 IPv617
AS29632Netassist International EOODUnclassifiedIPv68
AS112DNS-OARCUnclassifiedIPv4 IPv66
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv65
AS204092Association GRIFONUnclassifiedIPv4 IPv65

All 27 adjacent →

Provenance

Where this comes from

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