Data as of Nov 11, 2026

95.31.96.0/21

2 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
2
0.10% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
12
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

25 observations

Proxy providers listing exits

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.24.0.0/13
since Oct 2008
AS8402Residential200,108
11,080 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.64.0 - 95.31.111.25512,288CORBINA-BROADBAND-STATICStatic IP Poool for broadband customersASSIGNED 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.30.0.0/15

Routing history

Pattern
Stable
First seen
Dec 2010
Current origin since
Dec 2010 · 16 yr
Origin networks
1