Data as of Nov 14, 2026

95.129.168.0/22

19 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

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

Exits seen per day

2.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.129.169.0/24012
95.129.170.0/2407

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • GSocks
  • Geonix
  • Geonode
  • HideProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.129.168.0/212,048RU-SOVINTEL-20090220PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAOct 18, 2016abuse-b2b@beeline.ru
└ 95.129.168.0/221,024WBTNETADSL NetworkASSIGNED PAFeb 20, 2009abuse-b2b@beeline.ru
via RU-SOVINTEL-20090220

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 95.129.168.0/21

95.129.168.0/21

Routing history

Pattern
Stable
First seen
Mar 2009
Current origin since
Mar 2009 · 18 yr
Origin networks
1