Data as of Nov 12, 2026

95.27.240.0/22

4 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low
Recent change
New origin Aug 2026
its first announcement on record

Residential-proxy exits

Proxy exits
4
0.39% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
12
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

10 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.27.242.0/2402
95.27.241.0/2401
95.27.243.0/2401

Proxy providers listing exits

  • Byteful
  • GSocks
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxyma
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.26.0.0/15
since Dec 2010
AS8402Residential91,188
7,048 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 the announcement: those covering it, widest first, then every record inside it, 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.24.0.0 - 95.30.255.255458,752BEELINE-BROADBANDDynamic IP Pool for broadband customersASSIGNED PAMay 12, 2010abuse-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

Summary

Routing history

Pattern
Stable
First seen
Aug 2026
Current origin since
Aug 2026 · 3 mo
Origin networks
1