Data as of Nov 12, 2026

95.31.28.0/24

5 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
36
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.6K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Q2IP
  • Shifter
  • Thordata
  • VitalData
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.30.0.0/15
since Dec 2010
AS8402Residential2,511
279 always on
PJSC "Vimpelcom"
95.24.0.0/13
since Oct 2008
AS8402Residential200,239
11,259 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.0.0/198,192CORBINA-BROADBAND-STATICStatic IP Poool for broadband customers in MoscowASSIGNED PAMay 6, 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.0.0/19

Routing history

Pattern
Stable
First seen
Jan 2026
Current origin since
Jan 2026 · 10 mo
Origin networks
1