Data as of Nov 6, 2026
212.19.0.0/22
No anonymizer space · no proxy exits in 30 daysJSC 'Redcom-lnternet'
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 212.19.0.0/19 since May 2005 | AS8749 | Residential | 450 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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 212.19.0.0/19 | 8,192 | RU-REDCOM-980323 | JSC "Redcom-lnternet" (ORG-RA23-RIPE) · RU | ALLOCATED PA | — | abuse@ |
| └ 212. | 768 | REDCOM-NET | Redcom network | ASSIGNED PA | — | abuse@ via RU-REDCOM-980323 |
| └ 212.19.3.0/29 | 8 | REDCOM-SRV-DNS-2 | REDCOM Domain Name Servers second subnet | ASSIGNED PA | Aug 7, 2008 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.3.8/29 | 8 | REDCOM-NGN-EXT-1 | REDCOM NGN External addresses | ASSIGNED PA | Aug 7, 2008 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.3.16/28 | 16 | REDCOM-NGN-EXT-2 | REDCOM NGN External addresses | ASSIGNED PA | Aug 7, 2008 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.3.64/27 | 32 | REDCOM-NGN-EXT-4 | REDCOM NGN FW External Block | ASSIGNED PA | Jan 13, 2013 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.3.96/27 | 32 | REDCOM-SRV-WEBHOST-VIRTUAL | REDCOM Virtual Web Servers | ASSIGNED PA | Aug 7, 2008 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.3.128/26 | 64 | REDCOM-SRV-WEBHOST | REDCOM Physical Web Servers | ASSIGNED PA | Aug 7, 2008 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.3.192/26 | 64 | REDCOM-COLOCATION | REDCOM Colocation subnet | ASSIGNED PA | Aug 7, 2008 | abuse@ 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
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 960 | 94% | 1 | |
| Hosting | 64 | 6.3% | 1 |
Network & registry
Routing timeline
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- Feb 2025
- Current origin since
- Feb 2025 · 1.7 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 212.19.0.0/22 | AS8749 | /22 | RIPE | RPKI valid |
| 212.19.0.0/19 | AS8749 | /19 | RIPE | Too specific |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8749 | RIPE | REDCOM-MNT | Nov 5, 2025 |
Whois
Registration for this announcement
- Range
- 212.
19. 0. 0/ 19 - Netname
- RU-REDCOM-980323
- Registrant
- JSC "Redcom-lnternet"
- Registrant country
- RU
- Organization
- JSC "Redcom-lnternet" (ORG-RA23-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Not stated by the registry
- Updated
- Oct 28, 2026
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Mar 23, 1998
- Status
- assigned
Report abuse
Abuse contact
- abuse@
redcom. ru - Name
- REDCOM ABUSE
- Handle
- RA6664-RIPE