Data as of Nov 4, 2026
83.220.236.0/22
467 residential-proxy exits · 30 daysPJSC 'Vimpelcom'
Residential-proxy exits
Proxy exits
467
46% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
76
selling exits here
Oct 5, 2026 – Nov 3, 2026
Exits seen per day
7.4K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 83.220.237.0/24 | 0 | 130 | |
| 83.220.239.0/24 | 0 | 118 | |
| 83.220.236.0/24 | 0 | 111 | |
| 83.220.238.0/24 | 0 | 107 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPPeak
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonBright
- LemonLabs
- LemonPrime
- LudaxProxy
- MangoProxy
- Maskify
- NSocks
- NextProxy
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PrivateByte
- PrivateProxy
- ProxiesVision
- Proxio
- Proxiware
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- Shifter
- Smartproxy
- StrikeProxy
- Thordata
- VantageProxies
- VitalData
- 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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 83.220.224.0/19 | 8,192 | RU-BEE3G-20040407 | PJSC "Vimpelcom" (ORG-JA8-RIPE) · RU | ALLOCATED PA | Apr 7, 2004 | Internet. |
| └ 83.220.236.0/22 | 1,024 | BEE-MSK-GPRS-FW | Beeline-Moscow GPRS Firewall | ASSIGNED PA | Nov 13, 2008 | Internet. 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
Registry
Holder
- Organization
- PJSC "Vimpelcom"
- Handle
- ORG-JA8-RIPE
- Range
- 83.
220. 224. 0/ 19 - Registration type
- ALLOCATED PA
- Record created
- Apr 7, 2004
Origin network
AS16345
RU
- Name
- PJSC 'Vimpelcom'
- Type
- Internet provider
- Registered
- Mar 7, 2001
- Domain
- beeline.ru
- Industry
- Hosting and Cloud Provider
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Nov 2008
- Current origin since
- Nov 2008 · 18 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS16345 | RIPE | JSC "VimpelCom" | BEE-MNT | Nov 13, 2008 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 83.220.236.0/23 | AS16345 | RIPE | OJSC "VimpelCom" | BEE-MNT | Sep 16, 2013 |
| 83.220.238.0/23 | AS16345 | RIPE | OJSC "VimpelCom" | BEE-MNT | Sep 16, 2013 |
Whois
Registration for this announcement
- Range
- 83.
220. 236. 0/ 22 - Netname
- BEE-MSK-GPRS-FW
- Registrant
- Beeline-Moscow GPRS Firewall
- Registrant country
- RU
- Organization
- Beeline-Moscow GPRS Firewall
- Org country
- RU
- Type
- ASSIGNED PA
- Created
- Nov 13, 2008
- Updated
- Mar 10, 2025
- Maintainer
- BEE-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Apr 7, 2004
- Status
- assigned
Report abuse
Abuse contact
- Internet.
abuse@ beeline. ru - Name
- Vimpelcom Abuse Role
- Handle
- VAR23-RIPE