Observed topology
AS9038 BAT-AS9038
Mobile RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS9038: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,808 |
| AS8697 | Jordan Telecommunications PSC | Unclassified | IPv4 IPv6 | 2,796 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 2,200 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 2,165 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,592 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 367 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 284 |
| AS6777 | Amsterdam Internet Exchange B.V. | Unclassified | IPv4 | 50 |
| AS15802 | Emirates Integrated Telecommunications Company PJSC | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS9038 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8934 | National Information Technology Center | Unclassified | IPv4 | 758 |
| AS38968 | Abu-Ghazaleh Intellectual Property Ltd. | Unclassified | IPv4 | 301 |
| AS200666 | Palestine National Fund | Unclassified | IPv4 | 174 |
| AS206060 | Bank al Etihad Ltd | Unclassified | IPv4 | 146 |
| AS203357 | Emkanat Co for Software Development | Unclassified | IPv4 | 118 |
| AS51958 | The Royal Jordanian Airlines PLC | Unclassified | IPv4 | 111 |
| AS14789 | Cloudflare, Inc. | Unclassified | IPv4 IPv6 | 92 |
| AS208148 | Jordanian Experts for Information Security LLC | Unclassified | IPv4 IPv6 | 87 |
| AS35282 | Aramex International Services Jordan LLC | Unclassified | IPv4 | 59 |
| AS59451 | Al-Bank Al-Arabi PLC. CO. | Unclassified | IPv4 | 58 |
Adjacency
Adjacent networks
Every AS seen directly next to AS9038 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 3,680 |
| AS8697 | Jordan Telecommunications PSC | Unclassified | IPv4 IPv6 | 3,027 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 2,885 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 2,495 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 2,338 |
| AS8934 | National Information Technology Center | Unclassified | IPv4 | 758 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 393 |
| AS38968 | Abu-Ghazaleh Intellectual Property Ltd. | Unclassified | IPv4 | 301 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 288 |
| AS60849 | iLevant FZE | Residential | IPv4 | 174 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.