LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

31.11.48.0/21

41 residential-proxy exits · 30 days

Vodafone Qatar P.Q.S.C

Announcement
this exact prefix
RPKI valid
Announced by
AS211559
Type
Residential
69% of it

Residential-proxy exits

Proxy exits
41
2.0% of its addresses · 30 days
Always-on exits
9
22% of its exits
Spread
7 of 8
/24s with at least one exit
Providers
52
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

18K observations
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
31.11.54.0/24410
31.11.52.0/2435
31.11.48.0/24110
31.11.51.0/2419
31.11.49.0/2404
31.11.50.0/2402
31.11.53.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LemonBright
  • MangoProxy
  • Maskify
  • NSocks
  • NodeMaven
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • Webshare

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
31.11.48.0/212,048QA-VODAFONEQATAR-20110414Vodafone Qatar P.Q.S.C (ORG-VQQ1-RIPE) · QAALLOCATED PAApr 14, 2011abuse@vodafone.qa
└ 31.11.48.0/24256QA-VODAFONEQATARVodafone Qatar Q.S.C.ASSIGNED PAApr 10, 2016abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.49.0/24256QA-VODAFONEQATARVodafone Qatar Q.S.C.ASSIGNED PAApr 10, 2016abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.50.0 - 31.11.50.111112QA-VODAFONEQATARunknownASSIGNED PAOct 29, 2018abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.50.112/298QA-VODAFONEQATARunknownASSIGNED PAOct 29, 2018abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.50.120 - 31.11.50.255136QA-VODAFONEQATARunknownASSIGNED PAOct 29, 2018abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.51.0/24256QA-VODAFONEQATARVodafone Qatar Q.S.C.ASSIGNED PAApr 10, 2016abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.52.0/24256QA-VODAFONEQATARVodafone Qatar Q.S.C.ASSIGNED PAApr 10, 2016abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.53.0/24256QA-VODAFONEQATARVodafone Qatar Q.S.C.ASSIGNED PAApr 10, 2016abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.54.0/2664QA-VODAFONEQATARVodafone Qatar Q.S.CASSIGNED PAJul 24, 2019abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.54.64/2732QA-VODAFONEQATARunknownASSIGNED PAJul 24, 2019abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.54.96/2816QA-VODAFONEQATARVodafone Qatar Q.S.CASSIGNED PAJul 24, 2019abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.54.112/298QA-VODAFONEQATARVodafone Qatar Q.S.CASSIGNED PAJul 24, 2019abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.54.120/298QA-ASTAD_ENGINEERINGAstad Engineering CompanyASSIGNED PAJul 24, 2019abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.54.128/25128QA-VODAFONEQATARVodafone Qatar Q.S.CASSIGNED PAJul 24, 2019abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.55.0/2664QA-VODAFONEQATARVodafone Qatar Q.S.CASSIGNED PAJul 24, 2019abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.55.64/2732QA-ASTAD_ENGINEERINGAstad Engineering CompanyASSIGNED PAJul 24, 2019abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.55.96/2732QA-VODAFONEQATARVodafone Qatar Q.S.CASSIGNED PAJul 24, 2019abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414
└ 31.11.55.128/25128QA-VODAFONEQATARVodafone Qatar Q.S.CASSIGNED PAJul 24, 2019abuse@vodafone.qa
via QA-VODAFONEQATAR-20110414

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

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

2,048 addresses
TypeAddressesShareRanges
Residential1,41669%2
Business63231%12

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Jan 2016
Current origin since
Jul 2021 · 5.3 yr
Origin networks
2
Last change of origin
May 2022
Recorded history

History

Handoffs
2