Data as of Nov 13, 2026
80.82.32.0/19
278 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
278
3.4% of its addresses · 30 days
Always-on exits
17
6.1% of its exits
Spread
26 of 32
/24s with at least one exit
Providers
108
selling exits here
Oct 14, 2026 – Nov 12, 2026
Exits seen per day
82K observations
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 80.82.50.0/24 | 3 | 12 | |
| 80.82.39.0/24 | 2 | 15 | |
| 80.82.51.0/24 | 1 | 18 | |
| 80.82.61.0/24 | 1 | 16 | |
| 80.82.58.0/24 | 1 | 16 | |
| 80.82.37.0/24 | 1 | 15 | |
| 80.82.38.0/24 | 1 | 14 | |
| 80.82.45.0/24 | 1 | 12 | |
| 80.82.47.0/24 | 1 | 12 | |
| 80.82.46.0/24 | 1 | 11 | |
| 80.82.59.0/24 | 1 | 11 | |
| 80.82.40.0/24 | 1 | 10 | |
| 80.82.48.0/24 | 1 | 8 | |
| 80.82.33.0/24 | 1 | 3 | |
| 80.82.62.0/24 | 0 | 25 | |
| 80.82.54.0/24 | 0 | 20 | |
| 80.82.35.0/24 | 0 | 14 | |
| 80.82.49.0/24 | 0 | 11 | |
| 80.82.60.0/24 | 0 | 10 | |
| 80.82.63.0/24 | 0 | 9 | |
| 80.82.55.0/24 | 0 | 7 | |
| 80.82.44.0/24 | 0 | 3 | |
| 80.82.36.0/24 | 0 | 2 | |
| 80.82.43.0/24 | 0 | 2 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- APROXY
- ASHBURNPROXIES
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FLEETPROXY
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GloryCloud
- GoProxies
- GonzoProxy
- HELODATA
- HPROXY
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPROCKET_BASIC
- IPROCKET_PREMIUM
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LUMIPROXY
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MoMoProxy
- NSocks
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYLANE
- PROXYON
- PROXYSALE
- PROXYSCRAPE
- PROXYWING_BASIC
- PROXY_CC
- PrivateByte
- PrivateProxy
- Proxio
- Proxiware
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- StrikeProxy
- TORCHPROXIES_BASIC
- TORCHPROXIES_PREMIUM
- TORCHPROXIES_X
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
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 |
|---|---|---|---|---|---|---|
| 80.82.32.0/19 | 8,192 | RU-RTK-20010725 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Sep 3, 2002 | abuse@ |
| └ 80.82.53.184/30 | 4 | Zarechnoe-A-NET | OOO Zarechnoe | ASSIGNED PA | May 21, 2014 | abuse@ via RU-RTK-20010725 |
| └ 80.82.53.188/30 | 4 | Zarechnoe-B-NET | OOO Zarechnoe | ASSIGNED PA | May 21, 2014 | abuse@ via RU-RTK-20010725 |
| └ 80.82.53.192/27 | 32 | TECNOSTYLE-NET | TechnoStyle IT-Company | ASSIGNED PA | Oct 20, 2005 | abuse@ via RU-RTK-20010725 |
| └ 80.82.53.224/29 | 8 | MEDRK-NET | Voronezh MedRemKomplekt | ASSIGNED PA | May 17, 2006 | abuse@ via RU-RTK-20010725 |
| └ 80.82.53.232/29 | 8 | PERFOLIST-NET | OOO ZIF | ASSIGNED PA | Nov 25, 2005 | abuse@ via RU-RTK-20010725 |
| └ 80.82.53.240/30 | 4 | OO-TEHNOAVIA-NET | unknown | ASSIGNED PA | Sep 21, 2016 | abuse@ via RU-RTK-20010725 |
| └ 80.82.53.244/30 | 4 | JSC-Borhimmash-net | unknown | ASSIGNED PA | Sep 20, 2016 | abuse@ via RU-RTK-20010725 |
| └ 80.82.54.0/23 | 512 | VSI-FIX-ADDR | Fixed ip addresses for clients | ASSIGNED PA | Feb 17, 2011 | abuse@ via RU-RTK-20010725 |
| └ 80.82.56.0/25 | 128 | VSI-MSN | CenterTelecom Voronezh ISP | ASSIGNED PA | Mar 17, 2003 | abuse@ via RU-RTK-20010725 |
| └ 80.82.56.128/25 | 128 | VSI-MSN | CenterTelecom Voronezh ISP | ASSIGNED PA | Mar 22, 2003 | abuse@ via RU-RTK-20010725 |
| └ 80. | 48 | VSI-MSN | CenterTelecom Voronezh ISP | ASSIGNED PA | Mar 25, 2003 | abuse@ via RU-RTK-20010725 |
| └ 80. | 112 | VSI-MSN | CenterTelecom Voronezh ISP | ASSIGNED PA | Oct 8, 2004 | abuse@ via RU-RTK-20010725 |
| └ 80.82.57.192/26 | 64 | VSI-MSN-SW | CenterTelecom Voronezh ISP | ASSIGNED PA | Dec 25, 2003 | abuse@ via RU-RTK-20010725 |
| └ 80.82.58.0/23 | 512 | VSI-MSN-REGION | Regional multiservice network access | ASSIGNED PA | Mar 19, 2003 | abuse@ via RU-RTK-20010725 |
| └ 80.82.60.0/25 | 128 | VSI-MSN-REGION | Regional multiservice network access | ASSIGNED PA | Jul 9, 2008 | abuse@ via RU-RTK-20010725 |
| └ 80.82.61.0/24 | 256 | MACROREGIONAL_ | Regional multiservice network access | ASSIGNED PA | Jan 18, 2013 | abuse@ via RU-RTK-20010725 |
| └ 80.82.62.0/23 | 512 | VSI-FIX-ADDR | Fixed ip addresses for clients | ASSIGNED PA | Apr 13, 2011 | abuse@ via RU-RTK-20010725 |
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 | 7,020 | 86% | 38 | |
| Business | 1,156 | 14% | 175 | |
| Hosting | 16 | 0.20% | 1 |
Network & registry
Origin network
AS21017
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Jul 27, 2001
- Domain
- rostelecom.ru
- Industry
- Computer and Information Technology
- Spamhaus ASN-DROP
- not listed
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
Whois
Registration for this announcement
- Range
- 80.
82. 32. 0/ 19 - Netname
- RU-RTK-20010725
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Sep 3, 2002
- Updated
- May 25, 2026
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jul 25, 2001
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE