Data as of Nov 22, 2026

82.194.176.0/20

11 residential-proxy exits · 30 days

JSC RTComm.RU

Announcement
this exact prefix
No RPKI
Announced by
Type
Internet provider

Residential-proxy exits

Proxy exits
11
0.27% of its addresses · 30 days
Always-on exits
1
9.1% of its exits
Spread
2 of 16
/24s with at least one exit
Providers
51
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

2.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
82.194.191.0/2416
82.194.179.0/2405

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • DATAIMPULSE_PREMIUM
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • HASDATA
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • LemonBright
  • MangoProxy
  • NSocks
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
82.194.184.0/23
since Apr 2023
AS8920Internet providerJSC RTComm.RU
82.194.186.0/23
since Apr 2023
AS8920Internet providerJSC RTComm.RU
82.194.188.0/22
since Apr 2023
AS8920Internet provider6
1 always on
JSC RTComm.RU

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
82.194.160.0/198,192RU-RTCOMM-20031020JSC RTComm.RU (ORG-RA25-RIPE) · RUALLOCATED PAOct 20, 2003abuse@rtcomm.ru
└ 82.194.176.0/24256RTComm-DVRTComm.RU Khabarovsk networkASSIGNED PAJul 21, 2005abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.177.0/24256RTComm-DVRTComm.RU Khabarovsk networkASSIGNED PAJan 11, 2017abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.178.0/24256RTComm-DVRTComm.RU Khabarovsk networkASSIGNED PAMar 30, 2010abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.179.0/24256RTComm-DVRTComm.RU Khabarovsk networkASSIGNED PAAug 4, 2011abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.180.0/24256RTComm-DVRTComm.RU Khabarovsk networkASSIGNED PAAug 4, 2011abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.181.0/24256RTComm-DVRTComm.RU Khabarovsk networkASSIGNED PAAug 4, 2011abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.182.0/23512RTComm-DVRTComm.RU Khabarovsk networkASSIGNED PAFeb 11, 2009abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.184.0/23512RTComm-DVRTComm.RU Khabarovsk networkASSIGNED PAJan 12, 2017abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.186.0/24256RTComm-DVJSC RTComm.RU Khabarovsk networkASSIGNED PAJan 12, 2017abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.187.0/24256RTComm-DVJSC RTComm.RUASSIGNED PAJun 18, 2010abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.188.0/24256RTComm-DVJSC RTComm.RUASSIGNED PAJul 22, 2005abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.189.0/24256RTComm-DVJSC RTComm.RUASSIGNED PAJul 22, 2005abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.190.0/24256RTComm-DVJSC RTComm.RUASSIGNED PAJul 22, 2005abuse@rtcomm.ru
via RU-RTCOMM-20031020
└ 82.194.191.0/24256RTComm-DVJSC RTComm.RUASSIGNED PAApr 21, 2004abuse@rtcomm.ru
via RU-RTCOMM-20031020

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2007
Current origin since
Nov 2007 · 19 yr
Origin networks
1