Observed topology
AS203214 HulumTele Hulum Almustakbal Company for Communication Engineering and Services Ltd
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS203214: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS208293 | AlSalam State Company | Unclassified | IPv4 IPv6 | 40,249 |
Transit
Downstream networks
Networks for which AS203214 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS51684 | ASIACELL COMMUNICATIONS PJSC | Unclassified | IPv4 IPv6 | 3,285 |
| AS50597 | ScopeSky for communications, internet and technology services LLC | Unclassified | IPv4 | 1,771 |
| AS205889 | Giga Nineveh for internet services Ltd | Unclassified | IPv4 | 634 |
| AS212280 | Storm for Information Technology, Internet Services, Communications, Electronic Solutions, Software, and Automation LLC | Unclassified | IPv4 | 580 |
| AS58322 | Hala Al Rafidain Company for Communications and Internet LTD. | Unclassified | IPv4 | 460 |
| AS208365 | Shams Telecom Networks and Internet Service Ltd | Unclassified | IPv4 | 355 |
| AS14789 | Cloudflare, Inc. | Unclassified | IPv4 IPv6 | 353 |
| AS60815 | Data Net Telecom Co. Ltd | Unclassified | IPv4 | 342 |
| AS210838 | Nama Engineering & Projects (FZC) | Unclassified | IPv4 | 236 |
| AS50710 | Earthlink Telecommunications Equipment Trading & Services DMCC | Unclassified | IPv4 | 229 |
Adjacency
Adjacent networks
Every AS seen directly next to AS203214 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS208293 | AlSalam State Company | Unclassified | IPv4 IPv6 | 50,934 |
| AS51684 | ASIACELL COMMUNICATIONS PJSC | Unclassified | IPv4 IPv6 | 3,286 |
| AS50597 | ScopeSky for communications, internet and technology services LLC | Unclassified | IPv4 | 2,178 |
| AS205889 | Giga Nineveh for internet services Ltd | Unclassified | IPv4 | 693 |
| AS212280 | Storm for Information Technology, Internet Services, Communications, Electronic Solutions, Software, and Automation LLC | Unclassified | IPv4 | 638 |
| AS50710 | Earthlink Telecommunications Equipment Trading & Services DMCC | Unclassified | IPv4 | 573 |
| AS58322 | Hala Al Rafidain Company for Communications and Internet LTD. | Unclassified | IPv4 | 517 |
| AS60815 | Data Net Telecom Co. Ltd | Unclassified | IPv4 | 389 |
| AS208365 | Shams Telecom Networks and Internet Service Ltd | Unclassified | IPv4 | 355 |
| AS14789 | Cloudflare, Inc. | Unclassified | IPv4 IPv6 | 353 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.