asn.dev

Observed topology

AS59711 HZ-EU-AS HZ Hosting Ltd

Unclassified RIPE

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

Transit

Upstream networks

All 34

Networks observed carrying traffic for AS59711: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv63,082
AS174Cogent Communications, LLCTransitIPv4 IPv62,835
AS6939Hurricane Electric LLCTransitIPv4 IPv6815
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv6604
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6583
AS9002RETN LimitedUnclassifiedIPv4 IPv6561
AS6681GIVEME CLOUD SP Z O OHostingIPv4496
AS5511Orange S.A.TransitIPv4 IPv6240
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6180
AS24482SG.GSHostingIPv4 IPv6150

All 34 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215467Skhron OUHostingIPv4 IPv681
AS6681GIVEME CLOUD SP Z O OHostingIPv418

Adjacency

Adjacent networks

All 35

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv63,136
AS174Cogent Communications, LLCTransitIPv4 IPv62,843
AS6939Hurricane Electric LLCTransitIPv4 IPv6815
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv6604
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6583
AS9002RETN LimitedUnclassifiedIPv4 IPv6561
AS6681GIVEME CLOUD SP Z O OHostingIPv4537
AS5511Orange S.A.TransitIPv4 IPv6240
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6183
AS24482SG.GSHostingIPv4 IPv6151

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