asn.dev

Observed topology

AS8596 HOTZE-AS hotze.com GmbH

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8596: 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
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv4 IPv6128
AS6939Hurricane Electric LLCTransitIPv416
AS3303Swisscom (Schweiz) AGResidentialIPv44
AS8412T-Mobile Austria GmbHResidentialIPv44
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202516web-crossing GmbHUnclassifiedIPv4 IPv622

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv4 IPv6150
AS202516web-crossing GmbHUnclassifiedIPv4 IPv622
AS6939Hurricane Electric LLCTransitIPv416
AS3303Swisscom (Schweiz) AGResidentialIPv44
AS8412T-Mobile Austria GmbHResidentialIPv44
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv63

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-12 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.