Data as of Nov 8, 2026
87.229.224.0/19
155 residential-proxy exits · 30 daysPJSC 'Vimpelcom'
Residential-proxy exits
Proxy exits
155
1.9% of its addresses · 30 days
Always-on exits
18
12% of its exits
Spread
31 of 32
/24s with at least one exit
Providers
91
selling exits here
Oct 9, 2026 – Nov 7, 2026
Exits seen per day
43K observations
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- ASHBURNPROXIES
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- PacketStream
- PrivateProxy
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- Shifter
- Smartproxy
- StrikeProxy
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 87.229.128.0/17 since Feb 2009 | AS31359 | Mobile | 302 40 always on | PJSC "Vimpelcom" |
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 87.229.242.0/24 since Sep 2016 | AS3216 | Residential | 34 | PJSC "Vimpelcom" via PJSC "Vimpelcom" |
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 |
|---|---|---|---|---|---|---|
| 87.229.128.0/17 | 32,768 | RU-SOVINTEL-20050722 | PJSC "Vimpelcom" (ORG-ES15-RIPE) · RU | ALLOCATED PA | Jul 22, 2005 | abuse-b2b@ |
| └ 87.229.224.0/19 | 8,192 | RU-Vimpelcom-HQ-IPv4 | PJSC "Vimpelcom" (ORG-ES15-RIPE) · RU | LIR-PARTITIONED PA | Jun 20, 2013 | abuse-b2b@ |
| └ 87.229.224.0/24 | 256 | RU-SOVINTEL-Static-p2p-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Jun 20, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.225.0/24 | 256 | RU-SOVINTEL-MSK-Static-p2p-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Jun 20, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.226.0/24 | 256 | RU-SOVINTEL-p2p-Clients-static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Jun 26, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.228.0/24 | 256 | RU-SOVINTEL-FORATEC-Static-p2p-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Aug 7, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.229.0/24 | 256 | RU-SOVINTEL-p2p-and-Clients-Static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Aug 8, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.230.0/24 | 256 | RU-SOVAM-TelePort-p2p-and-xDSL-static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Aug 14, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.231.0/24 | 256 | RU-SOVINTEL-Static-IP-Pool-NET | 111250 Russia SVINTEL/EDN (Foratec) | ASSIGNED PA | Aug 20, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.232.0/24 | 256 | RU-SOVINTEL-Client-static-IP-Pool-NET | 111250 Russia SVINTEL/EDN (Foratec) | ASSIGNED PA | Aug 20, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.233.0/32 | 1 | RU-SOVAM-TelePort-Client-static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN (Foratec) | ASSIGNED PA | Aug 22, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.233.192/29 | 8 | RU-SOVINTEL-interface-NET | 111250 Russia Moscow | ASSIGNED PA | Aug 29, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.233.200/29 | 8 | RU-SOVINTEL-MSK-Energoservis-NET | Nizhnie Polya, 27, build. 11 | ASSIGNED PA | Aug 29, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.234.0/24 | 256 | RU-SOVINTEL-FoRaTeK-static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Sep 2, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.235.0/24 | 256 | RU-SOVINTEL-Foratek-Clients-static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Sep 2, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.236.0/24 | 256 | RU-SOVINTEL-Clients-static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Sep 9, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87. | 224 | RU-SOVINTEL-ForaTek-p2p-et-static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Nov 25, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.237.224/28 | 16 | RU-SOVINTEL-MSK-TP-LABS-NET | 108811 Russia Moscow, ZC-21750494 | ASSIGNED PA | Nov 25, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.237.240/28 | 16 | RU-SOVINTEL-ForaTek-p2p-et-static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Nov 25, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.238.0/24 | 256 | RU-SOVAM-p2p-et-Static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Sep 24, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.239.0/24 | 256 | RU-SOVAMTELEPORT-p2p-et-Static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Sep 16, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.240.0/24 | 256 | RU-SOVINTEL-p2p-et-Clients-static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Sep 24, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.241.0/24 | 256 | RU-EDN-SOVINTEL-Clients-Static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Sep 26, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.242.0/24 | 256 | RU-SOVINTEL-MSK-Wi-Fi-clients-IP-Pool-NET | 111250 Russia Mopscow SOVINTEL/EDN | ASSIGNED PA | Sep 26, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.243.0/24 | 256 | RU-SOVINTEL-MSK-CGN-IP-Pool-NET | 111250 Russia Mopscow SOVINTEL/EDN | ASSIGNED PA | Sep 26, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.244.0/24 | 256 | RU-SOVINTEL-xEthrnet-p2p-IPv4-pool-NET | 111250 Russia EDN/SOVINTEL | ASSIGNED PA | Apr 9, 2014 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.245.0/24 | 256 | RU-SOVAM-ForaTec-Client-static-IP-Pool-NET | 111250 Russia Mopscow SOVINTEL/EDN | ASSIGNED PA | Sep 26, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.246.0/24 | 256 | RU-SOVAM-ForaTec-Client-static-IP-Pool-NET | 111250 Russia Mopscow SOVINTEL/EDN | ASSIGNED PA | Sep 27, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.247.0/24 | 256 | RU-SOVINTEL-p2p-clients-IPv4-pool-NET | 111250 Russia EDN/SOVINTEL | ASSIGNED PA | Apr 9, 2014 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.248.0/24 | 256 | RU-SOVINTEL-ForaTec-Static-IP-Pool-NET | 111250 Russia Mopscow SOVINTEL/EDN | ASSIGNED PA | Oct 16, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.249.0/24 | 256 | RU-SOVAM-ForaTec-Client-static-IP-Pool-NET | 111250 Russia Mopscow SOVINTEL/EDN | ASSIGNED PA | Oct 16, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.250.0/24 | 256 | RU-SOVINTEL-p2p-et-WiFi-clients-IPv4-pool-NET | 111250 Russia EDN/SOVINTEL | ASSIGNED PA | Apr 9, 2014 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.251.0/24 | 256 | RU-GoldenTeleCom-ForaTec-Static-IP-Pool-NET | 111250 Russia Mopscow SOVINTEL/EDN | ASSIGNED PA | Oct 22, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.252.0/24 | 256 | RU-SOVINTEL-P2P-Client-Static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Oct 22, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.253.0/24 | 256 | RU-SOVINTEL-P2P-Client-Static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Oct 25, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
| └ 87.229.254.0/24 | 256 | RU-GoldenTeleCom-ForaTec-Static-IP-Pool-NET | 111250 Russia Mopscow SOVINTEL/EDN | ASSIGNED PA | Oct 25, 2013 | abuse-b2b@ via RU-Vimpelcom-HQ-IPv4 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
8,192 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 8,160 | >99% | 5 | |
| Business | 32 | 0.39% | 3 |
Network & registry
IPv4 market
Holder
- Organization
- PJSC "Vimpelcom"
- Handle
- ORG-ES15-RIPE
- Range
- 87.
229. 128. 0/ 17 - Registration type
- ALLOCATED PA
- Record created
- Jul 22, 2005
Origin network
AS3216
RU
- Name
- PJSC 'Vimpelcom'
- Type
- Internet provider
- Registered
- Apr 15, 1994
- Domain
- beeline.ru
- Website
- beeline.ru
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
- VPN servers
- 4
Routing timeline
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- Jun 2013
- Current origin since
- Jun 2013 · 13 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS3216 | RIPE | OJSC Vimpelcom HQ IP-address Pool | SOVINTEL-MNT | Mar 21, 2013 |
Whois
Registration for this announcement
- Range
- 87.
229. 224. 0/ 19 - Netname
- RU-Vimpelcom-HQ-IPv4
- Registrant
- PJSC "Vimpelcom"
- Registrant country
- RU
- Organization
- PJSC "Vimpelcom" (ORG-ES15-RIPE)
- Org country
- RU
- Type
- LIR-PARTITIONED PA
- Created
- Jun 20, 2013
- Updated
- Jun 20, 2013
- Maintainer
- SOVINTEL-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jul 22, 2005
- Status
- assigned
Report abuse
Abuse contact
- abuse-b2b@
beeline. ru - Name
- Sovintel Abuse Department
- Handle
- SVNT2-RIPE