asn.dev

Observed topology

AS211513 AH-EBL

Unclassified RIPE Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS211513: 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
AS210021DIL Technology LimitedResidentialIPv4 IPv693
AS212573FastIraq, LLCUnclassifiedIPv48

Transit

Downstream networks

inferred

Networks for which AS211513 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS208293AlSalam State CompanyUnclassifiedIPv4 IPv611,119
AS210021DIL Technology LimitedResidentialIPv4 IPv610,843
AS211181Civilisation Information Technology, communication and internet services Co., LTDUnclassifiedIPv4 IPv62,259
AS212088Al-Tair Al-Watani Company for General Trading, Agricultural Investments, Production and Distribution, Technical Services, Internet Services, Public Services, Information Technology and Software LtdUnclassifiedIPv42,118
AS212573FastIraq, LLCUnclassifiedIPv4236

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.