Data as of Nov 7, 2026
217.10.32.0/20
26 residential-proxy exits · 30 daysJSC Comcor
Residential-proxy exits
Proxy exits
26
0.63% of its addresses · 30 days
Always-on exits
8
31% of its exits
Spread
7 of 16
/24s with at least one exit
Providers
61
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
7.2K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 217.10.33.0/24 | 2 | 7 | |
| 217.10.46.0/24 | 2 | 3 | |
| 217.10.34.0/24 | 1 | 5 | |
| 217.10.41.0/24 | 1 | 5 | |
| 217.10.45.0/24 | 1 | 3 | |
| 217.10.42.0/24 | 1 | 2 | |
| 217.10.47.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- B2Proxy
- BartProxies
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- Decodo
- EnigmaProxy
- Evomi
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GloryCloud
- GonzoProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- LemonLabs
- LightningProxies
- MangoProxy
- MarsProxies
- NSocks
- NodeMaven
- NodeProxy
- NovaProxy
- Oxylabs
- PrivateProxy
- Proxies.fo
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyHat
- ProxyRack
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- Shifter
- SpyderProxy
- StrikeProxy
- ThunderProxy
- TrustProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
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 |
|---|---|---|---|---|---|---|
| 217.10.32.0/20 | 4,096 | RU-COMCOR-20000809 | JSC Comcor (ORG-CA35-RIPE) · RU | ALLOCATED PA | Feb 27, 2015 | netadm@ |
| └ 217.10.32.0/24 | 256 | AKADO-B2C-HFC | JSC "Akado-B2C" | ASSIGNED PA | Jun 16, 2004 | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.33.0/24 | 256 | AKADO-Stolitsa-HFC | JSC "AKADO-Stolitsa", DOCSIS ISP, Moscow | ASSIGNED PA | Jun 16, 2004 | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.34.0/24 | 256 | AKADO-Stolitsa-HFC | JSC "AKADO-Stolitsa", DOCSIS ISP, Moscow | ASSIGNED PA | Jun 16, 2004 | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.35.0/24 | 256 | AKADO-Stolitsa-HFC | JSC "AKADO-Stolitsa", DOCSIS ISP, Moscow | ASSIGNED PA | Jun 16, 2004 | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.36.0/24 | 256 | AKADO-STOLITSA-HFC | JSC Comcor (ORG-CA35-RIPE) · RU | ASSIGNED PA | Sep 10, 2015 | netadm@ |
| └ 217.10.37.0/24 | 256 | AKADO-Stolitsa-HFC | JSC "AKADO-Stolitsa", DOCSIS ISP, Moscow | ASSIGNED PA | — | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.38.0/24 | 256 | AKADO-Stolitsa-HFC | JSC Comcor (ORG-CA35-RIPE) · RU | ASSIGNED PA | May 31, 2002 | netadm@ |
| └ 217.10.39.0/24 | 256 | AKADO-Stolitsa-HFC | JSC "AKADO-Stolitsa", DOCSIS ISP, Moscow | ASSIGNED PA | May 30, 2002 | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.40.0/24 | 256 | AKADO-Stolitsa-HFC | JSC "AKADO-Stolitsa", DOCSIS ISP, Moscow | ASSIGNED PA | Oct 4, 2002 | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.41.0/24 | 256 | AKADO-Stolitsa-HFC | JSC "AKADO-Stolitsa", DOCSIS ISP, Moscow | ASSIGNED PA | Oct 4, 2002 | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.42.0/24 | 256 | AKADO-Stolitsa-HFC | JSC "AKADO-Stolitsa", DOCSIS ISP, Moscow | ASSIGNED PA | Oct 4, 2002 | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.43.0/24 | 256 | AKADO-Stolitsa-HFC | JSC "AKADO-Stolitsa", DOCSIS ISP, Moscow | ASSIGNED PA | Dec 15, 2003 | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.44.0/24 | 256 | AKADO-STOLITSA-HFC | public net at TECHNOLOGY-NET | ASSIGNED PA | Sep 10, 2015 | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.45.0/24 | 256 | AKADO-Stolitsa-HFC | JSC "AKADO-Stolitsa", DOCSIS ISP, Moscow | ASSIGNED PA | Dec 15, 2003 | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.46.0/24 | 256 | AKADO-Stolitsa-HFC | JSC "AKADO-Stolitsa", DOCSIS ISP, Moscow | ASSIGNED PA | Dec 24, 2003 | netadm@ via RU-COMCOR-20000809 |
| └ 217.10.47.0/24 | 256 | AKADO-Stolitsa-HFC | JSC "AKADO-Stolitsa", DOCSIS ISP, Moscow | ASSIGNED PA | Apr 20, 2004 | netadm@ via RU-COMCOR-20000809 |
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
Origin network
AS15582
RU
- Name
- JSC Comcor
- Type
- Internet provider
- Registered
- Aug 10, 2000
- Domain
- comcor.ru
- Industry
- Internet Service Provider (ISP)
- 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 · 21 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS15582 | RIPE | JSC "AKADO-Stolitsa" | COMTV-MNT | Mar 29, 2023 |
Whois
Registration for this announcement
- Range
- 217.
10. 32. 0/ 20 - Netname
- RU-COMCOR-20000809
- Registrant
- JSC Comcor
- Registrant country
- RU
- Organization
- JSC Comcor (ORG-CA35-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Feb 27, 2015
- Updated
- Nov 12, 2018
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Aug 9, 2000
- Status
- assigned
Report abuse
Abuse contact
- netadm@
comcor. ru - Name
- Abuse Contacts
- Handle
- AC23903-RIPE