LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

89.19.160.0/19

72 residential-proxy exits · 30 days

JSC Comcor

Announcement
this exact prefix
No RPKI
Announced by
AS15582
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
72
0.88% of its addresses · 30 days
Always-on exits
6
8.3% of its exits
Spread
12 of 32
/24s with at least one exit
Providers
79
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

14K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
89.19.177.0/24314
89.19.174.0/24111
89.19.180.0/2418
89.19.182.0/2415
89.19.178.0/24011
89.19.176.0/24010
89.19.173.0/2406
89.19.179.0/2403
89.19.160.0/2401
89.19.175.0/2401
89.19.181.0/2401
89.19.190.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • TalorData
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.19.160.0/198,192RU-COMCOR-20060824JSC Comcor (ORG-CA35-RIPE) · RUALLOCATED PAFeb 27, 2015netadm@comcor.ru
└ 89.19.160.0/212,048AKADO-B2CJSC "Akado-B2C"ASSIGNED PAAug 24, 2006netadm@comcor.ru
via RU-COMCOR-20060824
└ 89.19.168.0/23512TC-EXEJSC "AKADO-Stolitsa", TC-EXE, MoscowASSIGNED PAAug 24, 2006netadm@comcor.ru
via RU-COMCOR-20060824
└ 89.19.170.0/24256TC-EXEJSC "AKADO-Stolitsa", TC-EXE, MoscowASSIGNED PAAug 24, 2006netadm@comcor.ru
via RU-COMCOR-20060824
└ 89.19.171.0/24256TC-EXEJSC "AKADO-Stolitsa", TC-EXE, MoscowASSIGNED PAApr 16, 2009netadm@comcor.ru
via RU-COMCOR-20060824
└ 89.19.172.0/221,024TC-EXEJSC "AKADO-Stolitsa", TC-EXE, MoscowASSIGNED PAApr 16, 2009netadm@comcor.ru
via RU-COMCOR-20060824
└ 89.19.176.0/221,024TC-EXEJSC "AKADO-Stolitsa", TC-EXE, MoscowASSIGNED PAApr 16, 2009netadm@comcor.ru
via RU-COMCOR-20060824
└ 89.19.180.0/221,024TC-EXEJSC "AKADO-Stolitsa", TC-EXE, MoscowASSIGNED PAMay 4, 2009netadm@comcor.ru
via RU-COMCOR-20060824
└ 89.19.184.0/221,024TC-EXEJSC "AKADO-Stolitsa", TC-EXE, MoscowASSIGNED PAMay 4, 2009netadm@comcor.ru
via RU-COMCOR-20060824
└ 89.19.188.0/24256AKADO-STOLITSA-HFCpublic net at CMTS02-C01ASSIGNED PASep 10, 2015netadm@comcor.ru
via RU-COMCOR-20060824
└ 89.19.189.0/24256AKADO-STOLITSA-HFCpublic net at CMTS01-DD01ASSIGNED PASep 10, 2015netadm@comcor.ru
via RU-COMCOR-20060824

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2006
Current origin since
Apr 2014 · 13 yr
Origin networks
2
Last change of origin
Apr 2014
Recorded history

History

Handoffs
3