Data as of Nov 14, 2026

83.220.240.0/20

6 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
6
0.15% of its addresses · 30 days
Always-on exits
1
17% of its exits
Spread
6 of 16
/24s with at least one exit
Providers
41
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

849 observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FloppyData
  • GSocks
  • GeekProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • NodeProxy
  • NovaProxy
  • PSBProxy
  • PrivateByte
  • Proxmint
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • Shifter
  • SpyderProxy
  • VProxy
  • VantageProxies
  • 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
83.220.224.0/198,192RU-BEE3G-20040407PJSC "Vimpelcom" (ORG-JA8-RIPE) · RUALLOCATED PAApr 7, 2004Internet.abuse@beeline.ru
└ 83.220.240.0/204,096BEE_STATICAPN static.beeline.ruASSIGNED PAFeb 26, 2007Internet.abuse@beeline.ru
via RU-BEE3G-20040407

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