Data as of Nov 11, 2026

88.82.76.0/24

5 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
2
40% of its exits
Providers
37
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.7K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPRoyal
  • Infatica
  • Kookey
  • MangoProxy
  • NSocks
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • VitalProxy

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
88.82.64.0/198,192RU-SOVINTEL-20051216PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PADec 16, 2005abuse-b2b@beeline.ru
└ 88.82.76.0/24256Tatintelcom-ArcomTatintelcomASSIGNED PAFeb 9, 2006abuse-b2b@beeline.ru
via RU-SOVINTEL-20051216

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

Who has announced this prefix

Summary

Routing history

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