Data as of Nov 17, 2026

212.19.28.0/24

No anonymizer space · no proxy exits in 30 days

JSC 'Redcom-lnternet'

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

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 this block, widest first, each 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

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

212.19.28.0/22

Routing history

Pattern
Stable
First seen
Jul 2025
Current origin since
Jul 2025 · 1.3 yr
Origin networks
1