Data as of Nov 20, 2026

212.16.192.0/20

13 residential-proxy exits · 30 days

JSC RTComm.RU

Announcement
this exact prefix
No RPKI
Announced by
Type
Internet provider

Residential-proxy exits

Proxy exits
13
0.32% of its addresses · 30 days
Spread
5 of 16
/24s with at least one exit
Providers
56
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

1.1K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9HTTP
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • LUMIPROXY
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NovaProxy
  • PROXYLANE
  • PROXYSALE
  • PROXYSCRAPE
  • PROXY_CC
  • PrivateByte
  • Proxies.fo
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • RolaProxy
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.16.192.0/19
since May 2005
AS8920Internet provider16
1 always on
JSC RTComm.RU
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
212.16.192.0/22
since Aug 2016
AS8920Internet provider1JSC RTComm.RU
212.16.197.0/24
since Aug 2016
AS8920Internet providerJSC RTComm.RU
212.16.198.0/23
since Aug 2016
AS8920Internet providerJSC RTComm.RU
212.16.198.0/24
since Sep 2022
AS8920Internet providerJSC RTComm.RU
212.16.200.0/21
since Aug 2016
AS8920Internet provider7JSC RTComm.RU
212.16.203.0/24
since May 2005
AS8920Internet provider5JSC 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
212.16.192.0/198,192RU-RTCOMM-980806JSC RTComm.RU (ORG-RA25-RIPE) · RUALLOCATED PA—abuse@rtcomm.ru
└ 212.16.192.0/24256RTCJSC RTComm.RUASSIGNED PADec 20, 2001abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.193.0/24256RTCJSC RTComm.RUASSIGNED PADec 20, 2001abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.194.0/24256RTCJSC RTComm.RUASSIGNED PADec 20, 2001abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.195.0/24256RTCJSC RTComm.RUASSIGNED PAJan 12, 2017abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.198.0/24256RTCJSC RTComm.RUASSIGNED PAJan 12, 2017abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.199.0/24256RTCJSC RTComm.RUASSIGNED PAMay 11, 2008abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.202.0/24256RTCJSC RTComm.RUASSIGNED PADec 20, 2001abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.203.0/24256RTCJSC RTComm.RUASSIGNED PASep 28, 2003abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.204.0/24256RTCJSC VostoktelecomASSIGNED PAJun 10, 2002abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.205.0/24256RTCJSC RTComm.RUASSIGNED PAOct 17, 2003abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.207.0/24256RTCJSC VostoktelecomASSIGNED PAJul 11, 2005abuse@rtcomm.ru
via RU-RTCOMM-980806

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

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