e& · United Arab Emirates
e& is a mobile network operator in the United Arab Emirates, trading as etisalat by e& under the parent group e& (formerly Etisalat Group; Emirates Telecommunications Group Company PJSC). The registry documents AS5384 and AS8966 as carrying its mobile network, alongside seven other recorded ASNs, and lists MCC 424 with MNC 02. It runs 4G LTE and 5G.
Autonomous systems
Holder names and prefix counts come from the RIPE NCC's RIPEstat Data API, fetched on 2026-09-06. Role and confidence come from the evidence linked in each row; "confirmed" means a PeeringDB or RIPEstat record, or the operator's own site, names the operator.
| ASN | Holder (RIPEstat) | Role | Announced | IPv4 / IPv6 prefixes | Evidence |
|---|---|---|---|---|---|
| AS5384 | EMIRATES-INTERNET EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile network confirmed | yes | 2,391 / 2 | source · RIPEstat |
| AS8966 | Etisalat-AS EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC PeeringDB: Etisalat · NSP | Mobile network confirmed | yes | 49 / 7 | source · RIPEstat · PeeringDB |
| AS8959 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Role not documented confirmed | no | 0 / 0 | source · RIPEstat |
| AS8960 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC PeeringDB: SH-IX Fujairah Route Servers · Route Server | Enterprise / transit confirmed | no | 0 / 0 | source · RIPEstat · PeeringDB |
| AS8961 | SHIX-Dubai EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC PeeringDB: SH-IX Dubai Route Servers · Route Server | Enterprise / transit confirmed | no | 0 / 0 | source · RIPEstat · PeeringDB |
| AS59981 | ETISALAT-AS EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Role not documented confirmed | no | 0 / 0 | source · RIPEstat |
| AS59982 | ETISALAT-AS EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Role not documented confirmed | no | 0 / 0 | source · RIPEstat |
| AS59983 | ETISALAT-AS EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Role not documented confirmed | no | 0 / 0 | source · RIPEstat |
| AS199224 | ABUDHABISMARTHUB-AS EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Enterprise / transit confirmed | no | 0 / 0 | source · RIPEstat |
Mobile network codes
The MCC identifies the country and the MNC identifies the operator inside it. Together they appear in the IMSI of every SIM on the network and in device diagnostics; they are how a handset knows which network it is on.
About e&
The registry records nine ASNs for e&, all held by Emirates Telecommunications Group Company PJSC. Two of them carry mobile. AS5384, the Emirates Internet AS, announced 2,391 IPv4 prefixes against 2 IPv6 prefixes at the last probe, and AS8966 announced 49 IPv4 and 7 IPv6 prefixes. PeeringDB names AS8966 Etisalat with an information type of NSP, and it records AS8960 and AS8961 as the SmartHub IX route servers in Fujairah and Dubai. Those two and the five remaining ASNs announced no prefixes.
An address whose origin ASN is AS5384 or AS8966 is routed by e& in the United Arab Emirates. Both ASes originate mobile GPRS and LTE ranges alongside fixed broadband and transit prefixes, so the AS number alone does not settle whether an address is mobile, fixed or enterprise. AS8960, AS8961 and AS199224 are recorded as enterprise, while AS8959, AS59981, AS59982 and AS59983 have no documented role. None of those seven announced prefixes at the last probe, so they put no routed traffic in front of you to classify.
Research note. UAE consumer brand is 'e&' / 'etisalat by e&' (etisalat.ae redirects to eand.ae). RIPE holder for all Etisalat ASNs is ORG-ETC1-RIPE. AS5384 (EMIRATES-INTERNET, 'Public Internet Service', ~2,391 IPv4 prefixes, 2.4M IPs) is the main consumer AS: announced prefixes include netnames GPRS-EMIRNET 'Etisalat GPRS Network' (e.g. 31.218.140.0/23, 5.192.184.0/23) and LTE-1-EMIRNET 'Etisalat LTE Network' (31.219.34.0/23) alongside ETISALATADSL-EMIRNET fixed-broadband ranges, so it carries mobile AND fixed. AS8966 (Etisalat-AS, whois descr 'Emirates Internet Exchange Route Server', 49 IPv4 prefixes / 337k IPs announced) also originates GPRS-EMIRNET mobile ranges (31.219.177.128/25, 5.192.24.0/22) plus transit/CDN prefixes; treat as secondary mobile/transit AS. AS8960/8961 are SH-IX (SmartHub IX) route-server ASNs per PeeringDB, not consumer. AS8959, 59981, 59982, 59983, 199224 are registered to Etisalat but NOT announced per RIPEstat (AS8959 whois: 'Emirates Internet Exchange GTE Peer router, New York'); role unverifiable. No PeeringDB record exists for AS5384/8966/15802. MCC/MNC: only 424-02 (Etisalat, Emirates Telecom Corp, Operational, LTE 800/1800/2600, 5G 2500/3500; GSM shut down Dec 2023) is listed on Wikipedia's ITU 4xx table; candidate rows 430-02 and 431-02 are not listed for any UAE operator there and were dropped (not confirmed). Wikipedia 5G/LTE bands cite GSA. Generations: e& UAE page states '4G LTE ushered in the era of mobile internet... 150Mbps' and '5G speed is 10x faster than 4G... up to 1Gbps'; 5g-zte-launch page advertises 5.5G. Parent: eand.com news (21 Jun 2022) states 'etisalat by e&' is the new brand identity for Etisalat UAE under the Group (Etisalat Group rebranded to e& on 23 Feb 2022).
Checking whether an IP belongs to e&
Look up the origin ASN of the address and compare it with the table above. RIPEstat answers for any address, and the RADB whois mirror lists the routes registered under an ASN.
curl -s "https://stat.ripe.net/data/prefix-overview/data.json?resource=203.0.113.9" | jq '.data.asns'whois -h whois.radb.net -- '-i origin AS5384' | grep ^routeQuestions
What is e&'s ASN?
The registry records nine ASNs for e&, all registered to Emirates Telecommunications Group Company PJSC. AS5384 and AS8966 are the two documented as carrying mobile traffic, and AS5384 is much the wider of the pair by announced address space.
What is the MCC/MNC of e& in the UAE?
e& uses MCC 424 with MNC 02. That is the only network code pair the registry records for the operator in the United Arab Emirates. It identifies the network to handsets and roaming partners and has no bearing on which IP prefixes the operator announces.
Is an IP from AS5384 a mobile IP?
Not on that evidence alone. AS5384 is documented as carrying e&'s mobile network, but the same AS also originates fixed broadband and transit ranges, so an address in it can be a home line rather than a handset. Prefix-level detail is needed to tell them apart.
Sources
- https://www.eand.ae/en/index.html
- https://www.eand.com/en/news/21-june-2022-etisalat-by-enad.html
- https://www.eand.com/en/etisalat-uae.html
- https://en.wikipedia.org/wiki/Mobile_network_codes_in_ITU_region_4xx_(Asia)
- https://stat.ripe.net/data/as-overview/data.json?resource=AS5384
- https://stat.ripe.net/data/whois/data.json?resource=AS5384
- https://stat.ripe.net/data/routing-status/data.json?resource=AS5384
- https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS5384
- https://stat.ripe.net/data/whois/data.json?resource=31.218.140.0/23
- https://stat.ripe.net/data/whois/data.json?resource=31.219.34.0/23
- https://stat.ripe.net/data/as-overview/data.json?resource=AS8966
- https://stat.ripe.net/data/whois/data.json?resource=AS8966
- https://stat.ripe.net/data/routing-status/data.json?resource=AS8966
- https://stat.ripe.net/data/whois/data.json?resource=31.219.177.128/25
- https://stat.ripe.net/data/as-overview/data.json?resource=AS8959
- https://stat.ripe.net/data/whois/data.json?resource=AS8959
- https://www.peeringdb.com/api/net?asn=8960
- https://www.peeringdb.com/api/net?asn=8961
- https://stat.ripe.net/data/as-overview/data.json?resource=AS59981
- https://stat.ripe.net/data/as-overview/data.json?resource=AS59982
- https://stat.ripe.net/data/as-overview/data.json?resource=AS59983
- https://stat.ripe.net/data/as-overview/data.json?resource=AS199224
- https://www.eand.ae/en/c/support/mobile/5g/overview-and-benefits.html
- https://www.eand.ae/en/c/mobile/5g-zte-launch.html
- https://www.eand.ae/en/c/nwt-coverage-map-with-service.html
- RIPEstat Data API (holder, announced prefixes)
- PeeringDB API (network records)