Data as of Nov 17, 2026

212.19.16.0/23

21 residential-proxy exits · 30 days

JSC 'Redcom-lnternet'

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

Residential-proxy exits

Proxy exits
21
4.1% of its addresses · 30 days
Always-on exits
2
9.5% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
37
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

4.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.19.16.0/24221
212.19.17.0/2401

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • HPROXY
  • IPFly
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYFALL
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.19.0.0/19
since May 2005
AS8749Residential437
56 always on
JSC "Redcom-lnternet"

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.19.0.0/198,192RU-REDCOM-980323JSC "Redcom-lnternet" (ORG-RA23-RIPE) · RUALLOCATED PA—abuse@redcom.ru
└ 212.19.16.0/24256REDCOM-BB-7REDCOM Broadband Block 7ASSIGNED PASep 8, 2011abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.0/304REDCOM-CLNT-DKADKA COMPANY LtdASSIGNED PAJul 27, 2014abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.8/298REDCOM-CLNT-FlyAuroraJSC "Aurora Airlines"ASSIGNED PAApr 25, 2014abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.20/304REDCOM-CLNT-Polinom"Polinom" Co, ltdASSIGNED PAMar 15, 2012abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.24/298DELTALIZING-CLNT-REDCOMZAO "DeltaLizing"ASSIGNED PASep 20, 2006abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.32/298PRESENTDV-CLNT-REDCOMKompania Present Ltd.ASSIGNED PAAug 17, 2016abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.48/298REDCOM-CLNT-UstSrednekanGESStroi-Len57unknownASSIGNED PAOct 14, 2021abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.56/298REDCOM-CLNT-IVIunknownASSIGNED PANov 18, 2021abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.64/298REDCOM-CLNT-RusMyasoMolTorgunknownASSIGNED PADec 1, 2021abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.72/298REDCOM-CLNT-ESCORUSunknownASSIGNED PAFeb 2, 2022abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.80/298REDCOM-CLNT-SSMPunknownASSIGNED PADec 29, 2021abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.88/298REDCOM-CLNT-EMERCOM_RakitnoeunknownASSIGNED PADec 30, 2021abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.96/2732REDCOM-CLNT-N-KraftunknownASSIGNED PADec 6, 2019abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.128/2732INTOURKHAB-CLNT-REDCOMIntour-Khabarovsk networkASSIGNED PA—abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.160/298REDCOM-CLNT-SpektrunknownASSIGNED PAFeb 11, 2021abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.168/298REDCOM-CLNT-CVTCVT Co., ltdASSIGNED PAJun 3, 2013abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.176/2816REDCOM-CLNT-EMPState Unitary Enterprise EmporiumASSIGNED PAMar 27, 2002abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.192/2816REDCOM-CLNT-ViveyaunknownASSIGNED PADec 13, 2019abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.208/298REDCOM-CLNT-UdinskGoldunknownASSIGNED PAMar 17, 2021abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.216/298FE-AIRBASE-CLNT-REDCOMFar East Air Base for forest fire fightingASSIGNED PASep 5, 2003abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.17.224/2732REDCOM-CLNT-IPKSZPostgraduate Institute of Public Health Care SpecialistsASSIGNED PADec 4, 2018abuse@redcom.ru
via RU-REDCOM-980323

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
Jul 2025
Current origin since
Jul 2025 · 1.3 yr
Origin networks
1