asn.dev

Observed topology

AS210612 ASTEO_RED_NEUTRA

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS210612: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6102
AS174Cogent Communications, LLCTransitIPv4 IPv644
AS6939Hurricane Electric LLCTransitIPv4 IPv638
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv611
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS33891Core-Backbone GmbHHostingIPv43
AS25091IP-Max SAUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202513Gestioniza Infraestructuras S.L.ResidentialIPv4 IPv6256

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6356
AS202513Gestioniza Infraestructuras S.L.ResidentialIPv4 IPv6256
AS174Cogent Communications, LLCTransitIPv4 IPv644
AS6939Hurricane Electric LLCTransitIPv4 IPv638
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS33891Core-Backbone GmbHHostingIPv43
AS25091IP-Max SAUnclassifiedIPv61

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.