Data as of Nov 10, 2026

37.131.89.0/24

3 residential-proxy exits · 30 days

STC Bahrain B.S.C Closed

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
33
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 711Proxy
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FlashProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonBright
  • MangoProxy
  • Novada
  • Oxylabs
  • Proxio
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RapidProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.131.0.0/17
since Dec 2024
AS51375Residential5,416
748 always on
STC Bahrain B.S.C Closed

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
37.131.0.0/1732,768BH-VIVABH-20120221STC Bahrain B.S.C Closed (ORG-VBBC1-RIPE) · BHALLOCATED PAFeb 21, 2012abuse@stc.com.bh
└ 37.131.64.0/198,192BH-VIVABHBroadbandASSIGNED PAFeb 28, 2012abuse@stc.com.bh
via BH-VIVABH-20120221

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

Summary

Routing history

Pattern
Stable
First seen
Sep 2018
Current origin since
Sep 2018 · 8.1 yr
Origin networks
2
Last change of origin
Oct 2019
Recorded history

History

Handoffs
1