asn.dev

Observed topology

AS9038 BAT-AS9038 Al Bahrainia al Urdunia Liltaknia Wa Alitisalat Plc. Co

Mobile RIPE NSP

Upstreams 9 carry this network
Downstreams 27 this network carries
Adjacent (IPv4) 36
Adjacent (IPv6) 7
Upstream graph Who carries AS9038, and who carries them, drawn as a map up to the transit-free core. 6 exchanges Where AS9038 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS8697Jordan Telecommunications PSCUnclassifiedIPv4 IPv62,734
AS174Cogent Communications, LLCTransitIPv4 IPv62,714
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv62,240
AS6939Hurricane Electric LLCTransitIPv42,185
AS3257GTT Communications Inc.TransitIPv4 IPv61,561
AS6461Zayo BandwidthTransitIPv4416
AS33891Core-Backbone GmbHHostingIPv4371
AS49559A-Systems Sp. z o.o.UnclassifiedIPv450
AS15802Emirates Integrated Telecommunications Company PJSCUnclassifiedIPv41

Transit

Downstream networks

All 27

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

ASNetworkTypeFamiliesPaths seen
AS8934National Information Technology CenterUnclassifiedIPv4754
AS38968Abu-Ghazaleh Intellectual Property Ltd.UnclassifiedIPv4 IPv6496
AS200666Palestine National FundUnclassifiedIPv4177
AS206060Bank al Etihad LtdUnclassifiedIPv4146
AS203357Emkanat Co for Software DevelopmentUnclassifiedIPv4116
AS206608Islamic International Arab Bank PLCUnclassifiedIPv4116
AS51958The Royal Jordanian Airlines PLCUnclassifiedIPv4109
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv691
AS208148Jordanian Experts for Information Security LLCUnclassifiedIPv4 IPv684
AS35282Aramex International Services Jordan LLCUnclassifiedIPv458

All 27 downstreams →

Adjacency

Adjacent networks

All 36

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv63,683
AS8697Jordan Telecommunications PSCUnclassifiedIPv4 IPv63,074
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv62,971
AS3257GTT Communications Inc.TransitIPv4 IPv62,510
AS6939Hurricane Electric LLCTransitIPv42,342
AS8934National Information Technology CenterUnclassifiedIPv4754
AS38968Abu-Ghazaleh Intellectual Property Ltd.UnclassifiedIPv4 IPv6496
AS6461Zayo BandwidthTransitIPv4424
AS33891Core-Backbone GmbHHostingIPv4396
AS200666Palestine National FundUnclassifiedIPv4177

All 36 adjacent →

Provenance

Where this comes from

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