Data as of Nov 14, 2026

217.118.76.0/24

14 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
14
5.5% of its addresses · 30 days
Providers
26
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

142 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BlurPath
  • Byteful
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GSocks
  • GloryCloud
  • IPFly
  • IPPeak
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • Shifter
  • VitalExclusive

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
217.118.64.0/198,192RU-BEE3G-20010212PJSC "Vimpelcom" (ORG-JA8-RIPE) · RUALLOCATED PAJun 10, 2003Internet.abuse@beeline.ru
└ 217.118.76.0/24256BEEGPRSPE-1PJSC "VimpelCom"ASSIGNED PAFeb 9, 2017Internet.abuse@beeline.ru
via RU-BEE3G-20010212

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
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1