asn.dev

Observed topology

AS35492 FUNKFEUER FunkFeuer Wien - Verein zur Foerderung freier Netze

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35492: 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
AS8540AMA netwoRX GmbHUnclassifiedIPv499
AS47147Anexia Cloud Solutions GmbHUnclassifiedIPv4 IPv651
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv4 IPv629
AS6939Hurricane Electric LLCTransitIPv627
AS47692Nessus GmbHHostingIPv4 IPv619
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS3303Swisscom (Schweiz) AGResidentialIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS42729Verein zur Foerderung freier NetzeUnclassifiedIPv636

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8540AMA netwoRX GmbHUnclassifiedIPv499
AS47147Anexia Cloud Solutions GmbHUnclassifiedIPv4 IPv658
AS6939Hurricane Electric LLCTransitIPv656
AS42729Verein zur Foerderung freier NetzeUnclassifiedIPv636
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv4 IPv631
AS47692Nessus GmbHHostingIPv4 IPv621
AS1853ACONETUnclassifiedIPv44
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS3303Swisscom (Schweiz) AGResidentialIPv43

Provenance

Where this comes from

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