JSC Redcom-lnternet
REDCOM-DEDICATED-134
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 5 blocks across 5 clusters |
| Cluster ID | 208021655 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 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 |
|---|---|---|---|---|
| 46.183.134.0/24 | REDCOM-DEDICATED-134 | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “REDCOM DEDICATED” — 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.
- REDCOM-DEDICATED-5-2 1 blocks
- REDCOM-DEDICATED-4-1 1 blocks
- REDCOM-DEDICATED-26 1 blocks
- REDCOM-DEDICATED-5 1 blocks
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-DEDICATED-5-2 via JSC "Redcom-lnternet" sub-allocation
- REDCOM-DEDICATED-4-1 via JSC "Redcom-lnternet" sub-allocation
- REDCOM-DEDICATED-26 via JSC "Redcom-lnternet" sub-allocation
- REDCOM-DEDICATED-5 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
mnt-ru-redcom-rs-1
mnt-ru-redcom-telecom-1