Observed topology
AS8376 Jordan Data Communications Company LLC
Mobile RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8376: 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 |
|---|---|---|---|---|
| AS8697 | Jordan Telecommunications PSC | Unclassified | IPv4 IPv6 | 49,099 |
Transit
Downstream networks
Networks for which AS8376 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35656 | Jordanian Universities Network L.L.C. | Unclassified | IPv4 | 228 |
| AS59451 | Al-Bank Al-Arabi PLC. CO. | Unclassified | IPv4 | 115 |
| AS204327 | Network International Services Limited Jordan Company LLC | Unclassified | IPv4 | 78 |
| AS209029 | JORDAN LLC | Unclassified | IPv4 | 57 |
| AS212507 | Royal Hashemite Court | Unclassified | IPv4 | 57 |
| AS60838 | Jordan Islamic Bank Plc. Co. | Unclassified | IPv4 | 56 |
| AS206553 | Al-Hikma Pharmaceuticals LLC | Unclassified | IPv4 | 56 |
| AS209560 | Capital Bank of Jordan (Limited public shareholding) | Unclassified | IPv4 | 41 |
| AS38968 | Abu-Ghazaleh Intellectual Property Ltd. | Unclassified | IPv4 | 28 |
| AS197921 | Housing Bank for Trade and Finance PLC. | Unclassified | IPv4 | 22 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8376 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8697 | Jordan Telecommunications PSC | Unclassified | IPv4 IPv6 | 49,883 |
| AS35656 | Jordanian Universities Network L.L.C. | Unclassified | IPv4 | 228 |
| AS59451 | Al-Bank Al-Arabi PLC. CO. | Unclassified | IPv4 | 115 |
| AS204327 | Network International Services Limited Jordan Company LLC | Unclassified | IPv4 | 78 |
| AS209029 | JORDAN LLC | Unclassified | IPv4 | 57 |
| AS212507 | Royal Hashemite Court | Unclassified | IPv4 | 57 |
| AS60838 | Jordan Islamic Bank Plc. Co. | Unclassified | IPv4 | 56 |
| AS206553 | Al-Hikma Pharmaceuticals LLC | Unclassified | IPv4 | 56 |
| AS209560 | Capital Bank of Jordan (Limited public shareholding) | Unclassified | IPv4 | 41 |
| AS38968 | Abu-Ghazaleh Intellectual Property Ltd. | Unclassified | IPv4 | 28 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.