Data as of Nov 11, 2026

78.100.83.8/29

1 residential-proxy exit · 30 days

Ooredoo Q.S.C.

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
13% of its addresses · 30 days
Always-on exits
2
100% of its exits
Providers
35
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

2.8K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GloryCloud
  • IPFly
  • IPPeak
  • KindProxy
  • Kookey
  • LemonBright
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • PuraRoute
  • RapidProxy
  • Shifter
  • TalorData
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
78.100.0.0/15
since Jun 2007
AS8781Residential16,311
434 always on
Ooredoo Q.S.C.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
78.100.0.0/15131,072QA-QTEL-20070522Ooredoo Q.S.C. (ORG-QT1-RIPE) · QAALLOCATED PAMay 22, 2007abuse@qatar.net.qa
└ 78.100.83.8/298ELEMENT-DOHA-WESTBAY-HOTEL-PW620049unknownASSIGNED PANov 4, 2022abuse@qatar.net.qa
via QA-QTEL-20070522

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

78.100.80.0/20

Routing history

Pattern
Stable
First seen
Jun 2014
Current origin since
Jun 2014 · 12 yr
Origin networks
1