Data as of Nov 20, 2026

217.10.33.0/24

7 residential-proxy exits · 30 days

JSC Comcor

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
2
29% of its exits
Providers
45
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

4.2K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • VantageProxies
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.10.32.0/204,096RU-COMCOR-20000809JSC Comcor (ORG-CA35-RIPE) · RUALLOCATED PAFeb 27, 2015netadm@comcor.ru
└ 217.10.33.0/24256AKADO-Stolitsa-HFCJSC "AKADO-Stolitsa", DOCSIS ISP, MoscowASSIGNED PAJun 16, 2004netadm@comcor.ru
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

Routing timeline

Who has announced 217.10.32.0/20

217.10.32.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1