Data as of Nov 6, 2026
85.172.168.0/22
77 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
77
7.5% of its addresses · 30 days
Always-on exits
41
53% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
63
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
42K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 85.172.169.0/24 | 25 | 42 | |
| 85.172.168.0/24 | 16 | 32 | |
| 85.172.170.0/24 | 0 | 2 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- B2Proxy
- BartProxies
- BirdProxies
- BottingTools
- Bright Data
- ByteProxies
- Byteful
- CliProxy
- CoreProxy
- DataImpulse
- Decodo
- EnigmaProxy
- Evomi
- FlashProxy
- FloppyData
- GSocks
- Geonix
- Geonode
- GloryCloud
- GonzoProxy
- IPFly
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- Kookey
- LemonBright
- LemonPrime
- MangoProxy
- MarsProxies
- Maskify
- NSocks
- NextProxy
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PrivateProxy
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyRack
- ProxyWing
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- RolaProxy
- Shifter
- StrikeProxy
- Thordata
- ThunderProxy
- VantageProxies
- VitalExclusive
- Webshare
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 85.172.0.0/14 since Sep 2018 | AS12389 | Residential | 39,073 3,080 always on | PJSC Rostelecom |
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 85.172.168.0/23 since Sep 2024 | AS199096 | Residential | 74 41 always on | PJSC Rostelecom via VolgaLink Ltd | |
| 85.172.170.0/24 since Aug 2019 | AS33934 | Residential | 2 | PJSC Rostelecom via VolgaLink Ltd | |
| 85.172.171.0/24 | AS42610 | Residential | 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 |
|---|---|---|---|---|---|---|
| 85.172.0.0/14 | 262,144 | RU-RTK-20041222 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Dec 22, 2004 | abuse@ |
| └ 85.172.168.0/22 | 1,024 | VOLGALINK | VolgaLink Ltd | SUB-ALLOCATED PA | Aug 27, 2025 | abuse@ via RU-RTK-20041222 |
| └ 85.172.171.0/24 | 256 | Rostelecom_ | unknown | SUB-ALLOCATED PA | Aug 27, 2025 | abuse@ via VOLGALINK |
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
IPv4 market
Holder
- Organization
- PJSC Rostelecom
- Handle
- ORG-JR8-RIPE
- Range
- 85.
172. 0. 0/ 14 - Registration type
- ALLOCATED PA
- Record created
- Dec 22, 2004
- Reallocated to
- VolgaLink Ltd
- Reallocated range
- 85.
172. 168. 0/ 22 - Reallocation type
- SUB-ALLOCATED PA
- Reallocated
- Aug 27, 2025
Origin network
AS33934
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Sep 9, 2004
- Domain
- rt.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
- Apr 2006
- Current origin since
- Apr 2006 · 21 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 85.172.168.0/22 | AS33934 | /22 | RIPE | RPKI valid |
| 85.172.0.0/14 | AS12389 | /24 | RIPE | Another network |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS33934 | RIPE | VolgaLink Ltd | ROSTELECOM-MNT | Dec 11, 2024 |
Whois
Registration for this announcement
- Range
- 85.
172. 168. 0/ 22 - Netname
- VOLGALINK
- Registrant
- VolgaLink Ltd
- Registrant country
- RU
- Organization
- VolgaLink Ltd
- Org country
- RU
- Type
- SUB-ALLOCATED PA
- Created
- Aug 27, 2025
- Updated
- Aug 27, 2025
- Maintainer
- ROSTELECOM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Dec 22, 2004
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE