Data as of Nov 11, 2026

62.209.26.0/23

2 residential-proxy exits · 30 days

Zain Bahrain B.S.C.

Announcement
No RPKI
Announced by
Type
Mobile

Residential-proxy exits

Proxy exits
2
0.39% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
35
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

363 observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • GSocks
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
62.209.0.0/19
since Mar 2008
AS31452Mobile1,040
4 always on
Zain Bahrain B.S.C.
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
62.209.26.0/24
since Oct 2016
AS31452Mobile2Zain Bahrain B.S.C.
62.209.27.0/24
since May 2012
AS31452MobileZain Bahrain B.S.C.

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
62.209.0.0/198,192BH-MTC-20080201Zain Bahrain B.S.C. (ORG-MVB1-RIPE) · BHALLOCATED PAFeb 1, 2008abuse@bh.zain.com
└ 62.209.24.0/212,048BH-ZAINZain Bahrain IP AllocationASSIGNED PAOct 2, 2012abuse@bh.zain.com
via BH-MTC-20080201

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

62.209.16.0/20

Routing history

Pattern
Stable
First seen
Sep 2008
Current origin since
Sep 2008 · 18 yr
Origin networks
1