Observed topology
AS5384 EMIRATES-INTERNET EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC
Mobile RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS5384: 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 |
|---|---|---|---|---|
| AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile | IPv4 IPv6 | 22,557 |
Transit
Downstream networks
Networks for which AS5384 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202024 | TELECOMMUNICATIONS AND DIGITAL GOVERNMENT REGULATORY AUTHORITY | Unclassified | IPv4 IPv6 | 1,087 |
| AS201678 | Abu Dhabi Digital Authority | Unclassified | IPv4 | 956 |
| AS204832 | Data Hub Integrated Solutions Moro LLC | Unclassified | IPv4 | 299 |
| AS208797 | MASHREQBANK PJSC | Unclassified | IPv4 | 242 |
| AS61137 | Khalifa University | Unclassified | IPv4 | 238 |
| AS56479 | Higher Colleges of Technology | Unclassified | IPv4 | 187 |
| AS47862 | Khalifa University | Unclassified | IPv4 | 180 |
| AS200284 | FIRST ABU DHABI BANK P.J.S.C | Unclassified | IPv4 | 180 |
| AS51182 | The United Arab Emirates University | Unclassified | IPv4 | 177 |
| AS218669 | CORE42 TECHNOLOGY PROJECTS LLC | Unclassified | IPv4 | 122 |
Adjacency
Adjacent networks
Every AS seen directly next to AS5384 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile | IPv4 IPv6 | 27,681 |
| AS202024 | TELECOMMUNICATIONS AND DIGITAL GOVERNMENT REGULATORY AUTHORITY | Unclassified | IPv4 IPv6 | 1,087 |
| AS201678 | Abu Dhabi Digital Authority | Unclassified | IPv4 | 956 |
| AS204832 | Data Hub Integrated Solutions Moro LLC | Unclassified | IPv4 | 299 |
| AS208797 | MASHREQBANK PJSC | Unclassified | IPv4 | 242 |
| AS61137 | Khalifa University | Unclassified | IPv4 | 238 |
| AS56479 | Higher Colleges of Technology | Unclassified | IPv4 | 187 |
| AS47862 | Khalifa University | Unclassified | IPv4 | 180 |
| AS200284 | FIRST ABU DHABI BANK P.J.S.C | Unclassified | IPv4 | 180 |
| AS51182 | The United Arab Emirates University | Unclassified | IPv4 | 177 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.