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

212.19.28.0/22

45 residential-proxy exits · 30 days

JSC 'Redcom-lnternet'

Announcement
this exact prefix
RPKI valid
Announced by
AS8749
Type
Residential
>99% of it

Residential-proxy exits

Proxy exits
45
4.4% of its addresses · 30 days
Always-on exits
1
2.2% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
26
selling exits here
Oct 8, 2026 – Nov 6, 2026

Exits seen per day

2.6K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.19.30.0/24141
212.19.28.0/2401
212.19.31.0/2401

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.19.0.0/19
since May 2005
AS8749Residential447
62 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.28.32/298REDCOM-CLNT-ChernikovunknownASSIGNED PAMar 22, 2023abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.48/298REDCOM-CLNT-NevadaDV1unknownASSIGNED PANov 28, 2022abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.56/298REDCOM-CLNT-NevadaDV2unknownASSIGNED PANov 28, 2022abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.64/298REDCOM-CLNT-SolidBankunknownASSIGNED PAAug 8, 2022abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.72/298REDCOM-CLNT-SoftLineTrade1unknownASSIGNED PAJul 28, 2022abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.80/298REDCOM-CLNT-ProgrammyUchetaunknownASSIGNED PAJul 12, 2022abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.88/298REDCOM-CLNT-Nauka-SvyazunknownASSIGNED PAApr 12, 2023abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.96/2732REDCOM-CLNT-EMERCOMunknownASSIGNED PAJun 9, 2022abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.128/2816REDCOM-CLNT-MIACunknownASSIGNED PAJun 25, 2025abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.144/298REDCOM-CLNT-GorPoliclinikaZhDunknownASSIGNED PADec 10, 2025abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.152/298REDCOM-CLNT-GorPoliclinikaZhD-DOSunknownASSIGNED PAJan 12, 2026abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.160/298REDCOM-CLNT-AOSvyazunknownASSIGNED PAJun 15, 2025abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.168/298REDCOM-CLNT-FuelCompanyunknownASSIGNED PAApr 23, 2025abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.176/298REDCOM-CLNT-VolkovunknownASSIGNED PAMar 11, 2025abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.208/298REDCOM-CLNT-HospitalPiotrovichaunknownASSIGNED PAJun 26, 2023abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.216/304REDCOM-CLNT-ProgrammyUcheta1unknownASSIGNED PAApr 21, 2023abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.28.220/304REDCOM-CLNT-CLINIC2-2unknownASSIGNED PADec 9, 2022abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.30.0/24256REDCOM-BB-4REDCOM Broadband Block 4ASSIGNED PAJan 24, 2013abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.0/298REDCOM-CLNT-2K2K Company, Co ltdASSIGNED PAMay 31, 2012abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.8/298REDCOM-CLNT-SETTELECOM2SetTelecom Co., ltdASSIGNED PANov 20, 2013abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.16/2816REDCOM-CLNT-Satcom-Service-1unknownASSIGNED PAMay 12, 2021abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.32/2816REDCOM-CLNT-Satcom-Service-2unknownASSIGNED PAMay 12, 2021abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.48/2816REDCOM-CLNT-SatelecomDV-3unknownASSIGNED PAMar 13, 2018abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.64/2816HKIRO-CLNT-REDCOMunknownASSIGNED PAMar 30, 2017abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.80 - 212.19.31.11132REDCOM-CLNT-TechMontageCompany internal use (Service Installation Engineers)ASSIGNED PAJun 25, 2019abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.112/298ZEPTER-KHVZepter International RussiaASSIGNED PA—abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.120/298REDCOM-CLNT-KhabOilCompanyunknownASSIGNED PAMar 12, 2026abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.192/298REDCOM-CLNT-AxoftAxoft Inc.ASSIGNED PAApr 13, 2015abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.200/298REDCOM-CLNT-CorpSoftunknownASSIGNED PASep 28, 2022abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.208/2816REDCOM-CLNT-Mascom2OOO "Dscbi "Maskom"ASSIGNED PAMay 29, 2015abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.31.240/298REDCOM-CLNT-KatrenunknownASSIGNED PAJun 1, 2020abuse@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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

1,024 addresses
TypeAddressesShareRanges
Residential1,016>99%2
Business80.78%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Origin network

AS8749

RU
Name
JSC 'Redcom-lnternet'
Type
Internet provider
Registered
Apr 9, 1998
Domain
redcom.ru
Website
redcom.ru
Industry
Internet Service Provider (ISP)
Spamhaus ASN-DROP
not listed