asn.dev

Observed topology

AS212424 VIAREZO

Unclassified RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS212424: 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
AS31564Hexaglobe SASHostingIPv4 IPv690
AS6939Hurricane Electric LLCTransitIPv4 IPv635
AS9002RETN LimitedUnclassifiedIPv64
AS33891Core-Backbone GmbHHostingIPv44
AS24482SG.GSHostingIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv63
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv63
AS5405Inter.link GmbHUnclassifiedIPv42
AS12779IT.Gate S.p.A.UnclassifiedIPv42
AS20562Broadband Hosting B.V.HostingIPv42

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204515Association CransUnclassifiedIPv4 IPv644

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS31564Hexaglobe SASHostingIPv4 IPv690
AS6939Hurricane Electric LLCTransitIPv4 IPv660
AS204515Association CransUnclassifiedIPv4 IPv644
AS9002RETN LimitedUnclassifiedIPv68
AS33891Core-Backbone GmbHHostingIPv46
AS24482SG.GSHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv65
AS5405Inter.link GmbHUnclassifiedIPv43
AS12779IT.Gate S.p.A.UnclassifiedIPv43

All 15 adjacent →

Provenance

Where this comes from

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