asn.dev

Observed topology

AS29287 AT-WZN-AS Wien Energie

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29287: 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 IPv6330
AS6939Hurricane Electric LLCTransitIPv4 IPv673
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv68
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv67
AS33891Core-Backbone GmbHHostingIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25012WienIT GmbHUnclassifiedIPv459
AS206765ByteSource Technology Consulting GmbHUnclassifiedIPv459
AS202616Wien Energie GmbHUnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv4 IPv6438
AS6939Hurricane Electric LLCTransitIPv4 IPv681
AS25012WienIT GmbHUnclassifiedIPv459
AS206765ByteSource Technology Consulting GmbHUnclassifiedIPv459
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv614
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv68
AS33891Core-Backbone GmbHHostingIPv47
AS202616Wien Energie GmbHUnclassifiedIPv44

Provenance

Where this comes from

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