Data as of Nov 12, 2026

80.76.168.0/23

4 residential-proxy exits · 30 days

Vodafone Qatar P.Q.S.C

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
29
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

130 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
80.76.168.0/2402
80.76.169.0/2402

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • FlashProxy
  • GSocks
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • LemonBright
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.76.168.0/21
since Dec 2024
AS48728Mobile4Vodafone Qatar P.Q.S.C
80.76.160.0/20
since Dec 2024
AS48728Mobile363
29 always on
Vodafone Qatar P.Q.S.C
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
80.76.168.0/24
since Jul 2024
AS211559Residential2Vodafone Qatar P.Q.S.C
80.76.169.0/24
since Jul 2024
AS211559Residential2Vodafone Qatar P.Q.S.C

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
80.76.160.0/204,096QA-VODAFONEQATAR-20090114Vodafone Qatar P.Q.S.C (ORG-VQQ1-RIPE) · QAALLOCATED PAJan 14, 2009abuse@vodafone.qa
└ 80.76.168.0/24256QA-VODAFONEQATARVodafone Qatar Q.S.C.ASSIGNED PAApr 10, 2016abuse@vodafone.qa
via QA-VODAFONEQATAR-20090114
└ 80.76.169.0/24256QA-VODAFONEQATARVodafone Qatar Q.S.C.ASSIGNED PAApr 10, 2016abuse@vodafone.qa
via QA-VODAFONEQATAR-20090114

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
Nov 2021
Current origin since
Nov 2021 · 5.0 yr
Origin networks
1