Data as of Nov 7, 2026
82.196.128.0/19
88 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
88
1.1% of its addresses · 30 days
Always-on exits
12
14% of its exits
Spread
20 of 32
/24s with at least one exit
Providers
84
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
26K observations
- Residential
- Business
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 711Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- NSocks
- NextProxy
- NodeMaven
- NodeProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYWING_BASIC
- PacketStream
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RH7Proxy
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
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 |
|---|---|---|---|---|---|---|
| 82.196.128.0/19 | 8,192 | RU-RTK-20031031 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Nov 5, 2024 | abuse@ |
| └ 82.196.128.0/24 | 256 | CTCS-M10 | unknown | ASSIGNED PA | May 25, 2005 | abuse@ via RU-RTK-20031031 |
| └ 82.196.129.0/24 | 256 | CTCS-M9 | Centertelecom Service | ASSIGNED PA | May 20, 2005 | abuse@ via RU-RTK-20031031 |
| └ 82.196.130.0/27 | 32 | VOENTELECOM | FGUP "Voentelecom" | ASSIGNED PA | Jun 29, 2005 | abuse@ via RU-RTK-20031031 |
| └ 82.196.131.0/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.131.64/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.132.0/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.132.64/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.133.0/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.133.64/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.134.0/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.134.64/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.135.0/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.135.64/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.136.0/24 | 256 | RTL-VRN-PRFX | OJSC "RTLabs" | ASSIGNED PA | Apr 5, 2016 | abuse@ via RU-RTK-20031031 |
| └ 82.196.137.0/24 | 256 | RTL-VRN-PRFX | OJSC "RTLabs" | ASSIGNED PA | Jul 1, 2005 | abuse@ via RU-RTK-20031031 |
| └ 82.196.138.0/24 | 256 | RTL-RUM-PRFX | OJSC "RTLabs" | ASSIGNED PA | Sep 9, 2004 | abuse@ via RU-RTK-20031031 |
| └ 82.196.139.0/24 | 256 | RTL-RUM-PRFX | OJSC "RTLabs" | ASSIGNED PA | Dec 7, 2016 | abuse@ via RU-RTK-20031031 |
| └ 82.196.140.0/24 | 256 | CTCS | Centertelecom Service | ASSIGNED PA | Sep 9, 2004 | abuse@ via RU-RTK-20031031 |
| └ 82.196.141.0/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.141.64/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.142.0/24 | 256 | CTCS | Centertelecom Service | ASSIGNED PA | Sep 9, 2004 | abuse@ via RU-RTK-20031031 |
| └ 82.196.143.0/24 | 256 | RU-RTK-20031031 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | SUB-ALLOCATED PA | Dec 12, 2025 | abuse@ |
| └ 82.196.143.0/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.143.64/26 | 64 | CTCS | Centertelecom Service | ASSIGNED PA | Dec 18, 2003 | abuse@ via RU-RTK-20031031 |
| └ 82.196.144.0/24 | 256 | CTCS-M10 | Centertelecom Service | ASSIGNED PA | Feb 5, 2026 | abuse@ via RU-RTK-20031031 |
| └ 82.196.145.0/24 | 256 | RT-NET | unknown | ASSIGNED PA | Jan 13, 2026 | abuse@ via RU-RTK-20031031 |
| └ 82.196.152.0/22 | 1,024 | RTL-OFFCES-PRFX | OJSC "RTLabs" | ASSIGNED PA | Sep 9, 2004 | abuse@ via RU-RTK-20031031 |
| └ 82.196.156.0/24 | 256 | NN-JSC-Bryansktel | Bryansktel JSC | ASSIGNED PA | Oct 6, 2005 | abuse@ via RU-RTK-20031031 |
| └ 82.196.157.0/24 | 256 | RTK-NET | unknown | ASSIGNED PA | Jul 24, 2026 | abuse@ via RU-RTK-20031031 |
| └ 82.196.158.0/24 | 256 | CTCS-TECH-LOOPBACKS-1 | Centertelecom Service Corporate Network | ASSIGNED PA | Mar 14, 2006 | abuse@ via RU-RTK-20031031 |
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,264 | 89% | 9 | |
| Business | 928 | 11% | 15 |
Network & registry
Origin network
AS12389
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Jul 1, 2005
- Domain
- rt.ru
- Website
- www.company.rt.ru/en/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Reactivated
- First seen
- May 2005
- Current origin since
- Oct 2025 · 1.0 yr
- Origin networks
- 2
- Last change of origin
- Oct 2025
Recorded history
History
- Handoffs
- 1
Whois
Registration for this announcement
- Range
- 82.
196. 128. 0/ 19 - Netname
- RU-RTK-20031031
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Nov 5, 2024
- Updated
- Apr 17, 2025
- Maintainer
- ROSTELECOM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Oct 31, 2003
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE