asn.dev

Observed topology

AS211251 A1-DC A1 Internet BV

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS211251: 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
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv4256
AS57866Fusix Networks B.V.UnclassifiedIPv4176
AS44854Arend BrouwerHostingIPv4140
AS6939Hurricane Electric LLCTransitIPv456
AS1103SURF B.V.UnclassifiedIPv411
AS24482SG.GSHostingIPv411
AS34019Hivane AssociationUnclassifiedIPv411
AS34927iFog GmbHHostingIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv411

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203966A1 Internet BVUnclassifiedIPv452

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv4273
AS57866Fusix Networks B.V.UnclassifiedIPv4195
AS44854Arend BrouwerHostingIPv4144
AS6939Hurricane Electric LLCTransitIPv464
AS203966A1 Internet BVUnclassifiedIPv452
AS24482SG.GSHostingIPv412
AS34019Hivane AssociationUnclassifiedIPv412
AS34927iFog GmbHHostingIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv412
AS1103SURF B.V.UnclassifiedIPv411

Provenance

Where this comes from

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