Data as of Nov 16, 2026

217.114.239.0/24

11 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
11
4.3% of its addresses · 30 days
Always-on exits
3
27% of its exits
Providers
50
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

13K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PSBProxy
  • PrivateProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.114.224.0/204,096RU-SOVINTEL-20040809PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAAug 9, 2004abuse-b2b@beeline.ru
└ 217.114.239.0/24256FTTBDynamic FTTB users blockASSIGNED PAApr 9, 2008abuse-b2b@beeline.ru
via RU-SOVINTEL-20040809

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

Who has announced 217.114.238.0/23

217.114.238.0/23

Routing history

Pattern
Stable
First seen
Feb 2020
Current origin since
Feb 2020 · 6.8 yr
Origin networks
1