Data as of Nov 11, 2026

95.31.243.0/24

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
9
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

11 observations

Proxy providers listing exits

  • 711Proxy
  • B2Proxy
  • EZProxies
  • IPFly
  • IPPeak
  • MoMoProxy
  • PuraRoute
  • RainProxy
  • RoamProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.30.0.0/15
since Dec 2010
AS8402Residential2,512
276 always on
PJSC "Vimpelcom"
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 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.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

Summary

Routing history

Pattern
Stable
First seen
Jul 2012
Current origin since
Jul 2012 · 14 yr
Origin networks
1