Data as of Nov 5, 2026
82.162.192.0/18
83 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
83
0.51% of its addresses · 30 days
Always-on exits
2
2.4% of its exits
Spread
19 of 64
/24s with at least one exit
Providers
59
selling exits here
Oct 6, 2026 – Nov 4, 2026
Exits seen per day
8.8K observations
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 711Proxy
- Ake.net
- B2Proxy
- BartProxies
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- GSocks
- Geonix
- Geonode
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- Infatica
- InfiniteProxies
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- NextProxy
- NodeMaven
- NodeProxy
- NovaProxy
- Novada
- ProxiesVision
- Proxiware
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- ResiProxies
- Shifter
- Thordata
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 82.162.0.0/16 since May 2005 | AS12332 | Residential | 2,982 131 always on | PJSC Rostelecom |
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 82.162.252.0/24 since Aug 2020 | AS12389 | Residential | 61 | PJSC Rostelecom |
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.162.0.0/16 | 65,536 | RU-RTK-20030716 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Jul 16, 2003 | abuse@ |
| └ 82.162.192.0/24 | 256 | POL-ARTEM-NET | Artemovsky unit of electrical communications | ASSIGNED PA | Jul 24, 2003 | abuse@ via RU-RTK-20030716 |
| └ 82.162.193.0/24 | 256 | POL-ARTEM-NET | Artemovsky unit of electrical communications | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.194.0/24 | 256 | POL-PPPOE-NET-UNL | Static long-term lease ip range | ASSIGNED PA | Jul 17, 2012 | abuse@ via RU-RTK-20030716 |
| └ 82.162.195.0/24 | 256 | POL-ARTEM-NET | Artemovsky unit of electrical communications | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.196.0/24 | 256 | POL-KRASKINO-NET | UES of Slavyanka, Kraskino divizion | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.197.0/24 | 256 | POL-ARTEM-NET | PPPoE Customers | ASSIGNED PA | Apr 17, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.198.0/24 | 256 | POL-SLAVYANKA-NET | UES of Slavyanka | ASSIGNED PA | May 13, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.199.0/24 | 256 | POL-VNADEZHD-NET | Volno-Nadezhdinskiy node of electric communication | ASSIGNED PA | Jul 14, 2004 | abuse@ via RU-RTK-20030716 |
| └ 82.162.200.0/24 | 256 | POL-FOKINO-NET | UES of Fokino | ASSIGNED PA | Aug 2, 2004 | abuse@ via RU-RTK-20030716 |
| └ 82. | 512 | POL-BKAMEN-NET | UES of Bolshoy Kamen | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.203.0/24 | 256 | POL-FOKINO-NET | UES of Fokino | ASSIGNED PA | Mar 21, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.204.0/24 | 256 | POL-PLASTUN-NET | Terney node of electric communication | ASSIGNED PA | May 13, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.205.0/24 | 256 | POL-PLASTUN-NET | Plastun node of electric communication | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.206.0/24 | 256 | POL-KAVALEROVO-NET | Kavalerovo node of electric communication | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.207.0/24 | 256 | POL-OLGA-NET | Olginsky node of electric communication | ASSIGNED PA | Aug 2, 2004 | abuse@ via RU-RTK-20030716 |
| └ 82.162.208.0/23 | 512 | POL-DALNERECHENSK-NET | UES OF Dalnerechensk | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.210.0/24 | 256 | POL-LESOZAVODSK-NET | Lesozavodsky node of electric communication | ASSIGNED PA | Aug 8, 2004 | abuse@ via RU-RTK-20030716 |
| └ 82.162.211.0/24 | 256 | POL-LESOZAVODSK-DSL-NET | Lesozavodsky node of electric communication | ASSIGNED PA | Aug 9, 2004 | abuse@ via RU-RTK-20030716 |
| └ 82.162.212.0/24 | 256 | POL-LUCHEGORSK-NET | UES OF Luchegorsk | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.213.0/24 | 256 | POL-LESOZAVODSK-NET | Lesozavodsky node of electric communication | ASSIGNED PA | May 17, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.214.0/24 | 256 | POL-NOVOPOKROVKA-NET | UES OF Novopokrovka | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.215.0/24 | 256 | POL-NKLOZOVY-NET | Lozovy Local Electrocommunication Node | ASSIGNED PA | May 17, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.216.0/23 | 512 | POL-DALNERECHENSK-NET | UES OF Dalnerechensk | ASSIGNED PA | Apr 4, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.218.0/23 | 512 | POL-LESOZAVODSK-DSL-NET | Lesozavodsky node of electric communication | ASSIGNED PA | Apr 4, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.220.0/24 | 256 | POL-YAKOVLEVKA-NET | Yakovlevka Unit of Electrical Communications | ASSIGNED PA | May 13, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.221.0/24 | 256 | POL-CHERNIGOVKA-NET | UES of Chernigovka | ASSIGNED PA | May 13, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.222.0/24 | 256 | POL-KIROVKA-NET | UES of Kirovka | ASSIGNED PA | May 13, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.223.0/24 | 256 | POL-GORNYEKLUCHI-NET | UES of Kirovka | ASSIGNED PA | May 13, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82. | 1,536 | POL-NAKHODKA-NET | Nakhodka node of electric communication | ASSIGNED PA | Mar 30, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82. | 17 | POL-EVROSET-NET | Evroset' Riteil, Ltd. | ASSIGNED PA | Jul 26, 2011 | abuse@ via RU-RTK-20030716 |
| └ 82.162.230.48/28 | 16 | POL-RCB-NET | Royal Credit Bank | ASSIGNED PA | May 3, 2010 | abuse@ via RU-RTK-20030716 |
| └ 82.162.230.64/28 | 16 | POL-RCB-NET | Royal Credit Bank | ASSIGNED PA | May 3, 2010 | abuse@ via RU-RTK-20030716 |
| └ 82.162.230.144/28 | 16 | POL-MAKSIMUM-NET | Maksimum, Ltd. | ASSIGNED PA | May 19, 2011 | abuse@ via RU-RTK-20030716 |
| └ 82.162.230.208/28 | 16 | POL-ROSBANK-NET | Rosbank, Primorsky Department | ASSIGNED PA | Oct 25, 2011 | abuse@ via RU-RTK-20030716 |
| └ 82.162.230.240/28 | 16 | POL-ARGUMPLUS-NET | Argument-Plus, LTD | ASSIGNED PA | May 20, 2010 | abuse@ via RU-RTK-20030716 |
| └ 82.162.231.0/25 | 128 | POL-PPPOE-NET-UNL | Dynamic Broadband Clients. | ASSIGNED PA | Jul 17, 2012 | abuse@ via RU-RTK-20030716 |
| └ 82.162.231.144/28 | 16 | POL-IVANOVAKV-NET | Ivanova Kira V., Private Establishment | ASSIGNED PA | Oct 26, 2011 | abuse@ via RU-RTK-20030716 |
| └ 82.162.231.240/28 | 16 | POL-DVTU-NET | Public Office DVTU SMO, Ltd. | ASSIGNED PA | Jul 1, 2011 | abuse@ via RU-RTK-20030716 |
| └ 82.162.232.0/23 | 512 | POL-NAKHODKA-NET | Nakhodka node of electric communication | ASSIGNED PA | Mar 30, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.234.0/23 | 512 | POL-NAKHODKA-NET | Nakhodka node of electric communication | ASSIGNED PA | Mar 30, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.236.0/24 | 256 | POL-PREOBRAZHENIE-NET | Preobrazhensky node of electric communication | ASSIGNED PA | May 14, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.237.0/24 | 256 | POL-VLADALEX-NET | Vladimiro-Alexandrovsky node of electric communication | ASSIGNED PA | May 14, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.238.0/24 | 256 | POL-PARTIZANSK-NET | Partizansk node of electric communication | ASSIGNED PA | May 14, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.239.0/24 | 256 | POL-LAZO-NET | Lazo node of electric communication | ASSIGNED PA | May 14, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.240.0/22 | 1,024 | POL-SPASSK-NET | UES of SPASSK | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.244.0/24 | 256 | POL-NKEKATERINOVKA-NET | Ekaterinovka Local Electrocommunication Node | ASSIGNED PA | Mar 24, 2004 | abuse@ via RU-RTK-20030716 |
| └ 82. | 768 | POL-ARSENEV-NET | UES of Arsenev | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-RTK-20030716 |
| └ 82.162.248.0/22 | 1,024 | POL-UUES-DSL-NET | DSL Connections in Ussuriisk | ASSIGNED PA | Sep 14, 2004 | abuse@ via RU-RTK-20030716 |
| └ 82.162.252.0/23 | 512 | POL-USSTELSERV-NET | UssuriTeleServise LTD | ASSIGNED PA | Sep 21, 2004 | abuse@ via RU-RTK-20030716 |
| └ 82.162.254.0/23 | 512 | POL-UUES-DSL-NET | DSL Connections in Ussuriisk | ASSIGNED PA | May 25, 2004 | abuse@ via RU-RTK-20030716 |
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
16,384 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 16,255 | >99% | 10 | |
| Business | 129 | 0.79% | 8 |
Network & registry
Origin network
AS12332
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Mar 17, 1999
- Domain
- primorye.ru
- Industry
- Computer and Information Technology
- Spamhaus ASN-DROP
- not listed
Routing timeline
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2005
- Current origin since
- May 2005 · 21 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 82.162.0.0/16 | AS12332 | /18 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12332 | RIPE | PRIMORYE NET | PRIMORYE-NCC-MNT ROSTELECOM-MNT | Mar 14, 2019 |
Whois
Registration for this announcement
- Range
- 82.
162. 0. 0/ 16 - Netname
- RU-RTK-20030716
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Jul 16, 2003
- Updated
- Jun 23, 2023
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jul 16, 2003
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE