Data as of Nov 10, 2026

95.31.158.0/24

6 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
31
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

647 observations

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • IPPeak
  • Infatica
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.30.0.0/15
since Dec 2010
AS8402Residential2,519
309 always on
PJSC "Vimpelcom"
95.24.0.0/13
since Oct 2008
AS8402Residential200,355
13,839 always on
PJSC "Vimpelcom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.24.0.0/13524,288RU-CORBINA-20081010PJSC "Vimpelcom" (ORG-CTAM1-RIPE) · RUALLOCATED PAOct 10, 2008abuse-b2b@beeline.ru
└ 95.31.152.0 - 95.31.255.25526,624BEELINE-BROADBANDDynamic IP Pool for Broadband CustomersASSIGNED PAAug 31, 2011abuse-b2b@beeline.ru
via RU-CORBINA-20081010

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

95.31.156.0/22

Routing history

Pattern
Stable
First seen
Nov 2025
Current origin since
Nov 2025 · 1.0 yr
Origin networks
1