asn.dev

Observed topology

AS20751 ASN-AZISTA AZISTA GmbH

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20751: 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 GmbHUnclassifiedIPv4324
AS24953NETPLANET GmbHUnclassifiedIPv490
AS6939Hurricane Electric LLCTransitIPv481
AS3303Swisscom (Schweiz) AGResidentialIPv418
AS21385Trusted Network GmbHUnclassifiedIPv49
AS48362Stadtwerke FeldkirchResidentialIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12971Internet Viennaweb Service GmbHUnclassifiedIPv4354
AS47592AZISTA GmbHHostingIPv459
AS199205Huemer Data Center GmbHUnclassifiedIPv422
AS25101AZISTA GmbHUnclassifiedIPv411

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv4699
AS12971Internet Viennaweb Service GmbHUnclassifiedIPv4531
AS24953NETPLANET GmbHUnclassifiedIPv4197
AS6939Hurricane Electric LLCTransitIPv4194
AS47592AZISTA GmbHHostingIPv459
AS3303Swisscom (Schweiz) AGResidentialIPv444
AS199205Huemer Data Center GmbHUnclassifiedIPv433
AS48362Stadtwerke FeldkirchResidentialIPv412
AS25101AZISTA GmbHUnclassifiedIPv411
AS31543myNet GmbHResidentialIPv410

Provenance

Where this comes from

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