LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

87.254.136.0/21

8 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
87.254.128.0/19
No RPKI
Announced by
AS34038
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
8
0.39% of its addresses · 30 days
Always-on exits
1
13% of its exits
Spread
1 of 8
/24s with at least one exit
Providers
42
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.3K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

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.136.0/212,048COMTEL-TMN-NETComtel vpn client accessASSIGNED PAJan 17, 2007abuse-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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 87.254.128.0/19

87.254.128.0/19

Routing history

Pattern
Stable
First seen
Feb 2006
Current origin since
Feb 2006 · 21 yr
Origin networks
1