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

178.153.138.0/23

37 residential-proxy exits · 30 days

Ooredoo Q.S.C.

Announcement
178.153.128.0/20
RPKI valid
Announced by
AS8781
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

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

Exits seen per day

90 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.153.138.0/24023
178.153.139.0/24015

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • AnyIP
  • B2Proxy
  • BottingTools
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • Geonode
  • GloryCloud
  • HideProxy
  • IPPeak
  • LemonBright
  • LudaxProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • ProxiesVision
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • RainProxy
  • SPYDERPROXY_BASIC
  • SwiftProxy
  • ThunderProxy
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.152.0.0/15
since Aug 2010
AS8781Residential21,924
440 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
178.152.0.0/15131,072QA-QTEL-20100423Ooredoo Q.S.C. (ORG-QT1-RIPE) · QAALLOCATED PAApr 23, 2010abuse@qatar.net.qa
└ 178.153.128.0/1732,768WBC-BRAS-POOL-6unknownASSIGNED PAFeb 11, 2012abuse@qatar.net.qa
via QA-QTEL-20100423

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

178.153.128.0/20

Routing history

Pattern
Rotating
First seen
Apr 2012
Current origin since
Oct 2022 · 4.1 yr
Origin networks
2
Last change of origin
Oct 2022
Recorded history

History

Handoffs
3