Data as of Nov 12, 2026

5.192.24.0/22

6 residential-proxy exits · 30 days

Emirates Telecommunications Group Company (Etisalat Group) PJSC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
6
0.59% of its addresses · 30 days
Always-on exits
1
17% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
29
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

3.2K observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • Kookey
  • LemonBright
  • Oxylabs
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • ResiProxies
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.192.24.0/21
since Apr 2026
AS8966Mobile6
1 always on
Emirates Telecommunications Group Company (Etisalat Group) PJSC
5.192.0.0/18
since Oct 2014
AS5384Mobile3,021
6 always on
Emirates Telecommunications Group Company (Etisalat Group) PJSC
5.192.0.0/17
since Mar 2020
AS5384Residential16,695
313 always on
Emirates Telecommunications Group Company (Etisalat Group) PJSC
5.192.0.0/16
since Mar 2017
AS5384Residential17,081
313 always on
Emirates Telecommunications Group Company (Etisalat Group) PJSC

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.192.0.0 - 5.194.251.255195,584AE-EMIRNET-20120822Emirates Telecommunications Group Company (Etisalat Group) PJSC (ORG-ETC1-RIPE) · AEALLOCATED PASep 8, 2016abuse@emirates.net.ae
└ 5.192.0.0/1665,536GPRS-EMIRNETEmirates Telecommunications CorporationASSIGNED PADec 18, 2014abuse@emirates.net.ae
via AE-EMIRNET-20120822

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Apr 2026
Current origin since
Apr 2026 · 7 mo
Origin networks
1