JSC Redcom-lnternet

REDCOM-CLNT-MetallExport

BGP inherited

Cluster stats

Netblocks	1
All fragments	82 blocks across 82 clusters
Cluster ID	205355012
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 3 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (1)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
212.19.27.96/29	REDCOM-CLNT-MetallExport	RIPE	ASSIGNED PA	● medium

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “REDCOM CLNT” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Combined view of all 82 name-family clusters →

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

REDCOM-CLNT-2K via JSC "Redcom-lnternet" sub-allocation
Abonpos via JSC "Redcom-lnternet" sub-allocation
Polinom via JSC "Redcom-lnternet" sub-allocation
Dirdorstroy via JSC "Redcom-lnternet" sub-allocation
Amurship via JSC "Redcom-lnternet" sub-allocation
REDCOM-CLNT-LANITPARNER2 via JSC "Redcom-lnternet" sub-allocation
Khabstat via JSC "Redcom-lnternet" sub-allocation
REDCOM-CLNT-CVT via JSC "Redcom-lnternet" sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (1 of 1)

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE REDCOM-MNT