asn.dev

Observed topology

AS209835 AVANZAFIBRA

Residential RIPE

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS209835: 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
AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALUnclassifiedIPv4 IPv6713
AS35699Adamo Telecom Iberia S.A.UnclassifiedIPv4431
AS6939Hurricane Electric LLCTransitIPv4162
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6118
AS59908BalaLink S.A.UnclassifiedIPv4112
AS33891Core-Backbone GmbHHostingIPv459
AS50304Blix Solutions ASUnclassifiedIPv448
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv634
AS12859BIT BVHostingIPv424
AS20764CJSC RASCOMUnclassifiedIPv424

All 15 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALUnclassifiedIPv4 IPv6713
AS35699Adamo Telecom Iberia S.A.UnclassifiedIPv4431
AS6939Hurricane Electric LLCTransitIPv4162
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6118
AS59908BalaLink S.A.UnclassifiedIPv4112
AS33891Core-Backbone GmbHHostingIPv459
AS50304Blix Solutions ASUnclassifiedIPv448
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv634
AS12859BIT BVHostingIPv424
AS20764CJSC RASCOMUnclassifiedIPv424

All 15 adjacent →

Provenance

Where this comes from

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