Data as of Nov 16, 2026

212.19.8.0/21

169 residential-proxy exits · 30 days

JSC 'Redcom-lnternet'

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

Residential-proxy exits

Proxy exits
169
8.3% of its addresses · 30 days
Always-on exits
16
9.5% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
121
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

58K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BUYPERSONALPROXY
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LITPORT_LIMA
  • LOKIPROXY
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIES.RIP
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PacketStream
  • PrivateProxy
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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.15.0/2816REDCOM-CLNT-PerinatalCenterunknownASSIGNED PAApr 30, 2021abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.16/298REDCOM-CLNT-KOMPLITunknownASSIGNED PAOct 30, 2019abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.24/298REDCOM-CLNT-CorpVozdDvizheniyaunknownASSIGNED PAJan 17, 2019abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.32/298REDCOM-CLNT-SakhalinEngineeringunknownASSIGNED PASep 20, 2021abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.40/298REDCOM-CLNT-UstSrednekanGESStroiunknownASSIGNED PASep 21, 2021abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.48/298REDCOM-CLNT-UNICOMOOO "UK Unicom"ASSIGNED PAFeb 5, 2015abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.56/298REDCOM-CLNT-KhabStatFederal State Statistics ServiceASSIGNED PAOct 31, 2013abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.64 - 212.19.15.9128KHABADM-CLNT-REDCOMKhabarovsk city administrationASSIGNED PAMar 15, 2012abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.96/298REDCOM-CLNT-ToguDVunknownASSIGNED PASep 9, 2026abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.104/298REDCOM-CLNT-MyasoOtpTorgunknownASSIGNED PAAug 9, 2024abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.112/2816REDCOM-CLNT-Satcom-Service-3unknownASSIGNED PAApr 29, 2022abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.128/304REDCOM-CLNT-KailosKailos LtdASSIGNED PAApr 15, 2015abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.132/304REDCOM-CLNT-KHNPJSC KhabarovskhefteproductASSIGNED PAMar 25, 2014abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.136/298LANITPARNER-CLNT-REDCOMZAO "Lanit-Partner"ASSIGNED PAAug 27, 2004abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.144/298REDCOM-CLNT-ClinicalHospitalunknownASSIGNED PAOct 10, 2019abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.152/298REDCOM-CLNT-LANITPARNER2ZAO "Lanit-Partner"ASSIGNED PASep 12, 2013abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.160/2816REDCOM-CLN-KHABAROVSKADM2unknownASSIGNED PAJan 9, 2017abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.184/298REDCOM-CLNT-KhabCityPowerNetworkJSC "Khabarovsk city power network"ASSIGNED PAJun 30, 2014abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.192/298REDCOM-CLNT-HawleunknownASSIGNED PANov 10, 2022abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.200/298REDCOM-CLNT-RZD-MedicineunknownASSIGNED PASep 20, 2020abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.208/2816REDCOM-CLNT-SatelecomDV-4unknownASSIGNED PAFeb 27, 2019abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.15.224/2732REDCOM-CLNT-SatelecomDV-2unknownASSIGNED PAMar 12, 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