Data as of Nov 19, 2026

212.19.25.0/24

No anonymizer space · no proxy exits in 30 days

JSC 'Redcom-lnternet'

Announcement
this exact prefix
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
AS8749Residential440
57 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.25.0/25128REDCOM-NET-MPLSLinks1MPLS routers backbone p2p networksASSIGNED PAMar 13, 2009abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.25.128/2664REDCOM-NET-PoP-LANsCascade LANs on remote points of precenseASSIGNED PAMar 26, 2008abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.25.192/2664REDCOM-BB-UNLIM-SUBBLOCK-2REDCOM Broadband SubBlock 2ASSIGNED PAJan 17, 2013abuse@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
Feb 2025
Current origin since
Feb 2025 · 1.8 yr
Origin networks
1