asn.dev

Observed topology

AS211526 DAEU-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS211526: 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
AS13335Cloudflare, Inc.HostingIPv4128
AS8717A1 Bulgaria EADResidentialIPv460
AS8866Vivacom Bulgaria EADResidentialIPv637

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12564Council of MinistersUnclassifiedIPv4366
AS25554Ministry of Finance of Bulgarian GovernmentUnclassifiedIPv4122
AS204842Ministry of Justice BulgariaUnclassifiedIPv461
AS206645Ministry of Regional Development and Public WorksUnclassifiedIPv428
AS203484ROAD INFRASTRUCTURE AGENCYUnclassifiedIPv423

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8866Vivacom Bulgaria EADResidentialIPv4 IPv6636
AS12564Council of MinistersUnclassifiedIPv4427
AS13335Cloudflare, Inc.HostingIPv4128
AS25554Ministry of Finance of Bulgarian GovernmentUnclassifiedIPv4122
AS8717A1 Bulgaria EADResidentialIPv476
AS8262Evolink EADUnclassifiedIPv461
AS204842Ministry of Justice BulgariaUnclassifiedIPv461
AS206645Ministry of Regional Development and Public WorksUnclassifiedIPv428
AS203484ROAD INFRASTRUCTURE AGENCYUnclassifiedIPv423
AS3257GTT Communications Inc.TransitIPv417

Provenance

Where this comes from

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