asn.dev

Observed topology

AS58322 halasat Hala Al Rafidain Company for Communications and Internet LTD.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58322: 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
AS203214Hulum Almustakbal Company for Communication Engineering and Services LtdUnclassifiedIPv4476

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208131Cloud Company for General Services LtdUnclassifiedIPv460
AS210509Optimum Line for Internet Services Ltd.UnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS203214Hulum Almustakbal Company for Communication Engineering and Services LtdUnclassifiedIPv4595
AS208131Cloud Company for General Services LtdUnclassifiedIPv460
AS210509Optimum Line for Internet Services Ltd.UnclassifiedIPv459

Provenance

Where this comes from

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