Data as of Nov 16, 2026

87.254.133.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
Always-on exits
1
17% of its exits
Providers
37
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

5.1K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.254.128.0/19
since Feb 2006
AS34038Mobile20
3 always on
PJSC "Vimpelcom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
87.254.128.0/198,192RU-SOVINTEL-20051020PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAOct 20, 2005abuse-b2b@beeline.ru
└ 87.254.133.0/24256RU-BeeLine-B2B-client-IP-pool-NET111250 Russia BeeLiNe et COMTELASSIGNED PASep 11, 2008abuse-b2b@beeline.ru
via RU-SOVINTEL-20051020

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

87.254.132.0/23

Routing history

Pattern
Stable
First seen
Jul 2019
Current origin since
Jul 2019 · 7.4 yr
Origin networks
1