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

62.209.28.0/24

2 residential-proxy exits · 30 days

Zain Bahrain B.S.C.

Announcement
this exact prefix
No RPKI
Announced by
AS31452
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
21
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

146 observations

Proxy providers listing exits

  • 9Proxy
  • BottingTools
  • CatProxies
  • CliProxy
  • Geonode
  • HPROXY
  • HideProxy
  • InfiniteProxies
  • LudaxProxy
  • MoMoProxy
  • NextProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • ProxiesVision
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_BASIC
  • Thordata
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
62.209.16.0/20
since Sep 2008
AS31452Mobile7Zain Bahrain B.S.C.
62.209.0.0/19
since Mar 2008
AS31452Mobile1,039
5 always on
Zain Bahrain B.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
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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Oct 2011
Current origin since
Oct 2011 · 15 yr
Origin networks
1