Data as of Nov 10, 2026

83.220.232.0/22

2 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
2
0.20% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
23
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

789 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.220.233.0/2401
83.220.235.0/2401

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VantageProxies
  • VibeProxies
  • 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
83.220.224.0/198,192RU-BEE3G-20040407PJSC "Vimpelcom" (ORG-JA8-RIPE) · RUALLOCATED PAApr 7, 2004Internet.abuse@beeline.ru
└ 83.220.232.0/221,024BEE_STATICAPN static.beeline.ruASSIGNED PAMay 5, 2009Internet.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
Jul 2009
Current origin since
Jul 2009 · 17 yr
Origin networks
1