RTCOMM-NTI
Cluster stats
| Netblocks | 5 |
| All fragments | 259 blocks across 100 clusters |
| Cluster ID | 193914713 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 213.24.64.128/25 | RTCOMM-NTI | RIPE | ASSIGNED PA | ● low |
| 213.24.160.80/28 | RTCOMM-NTI | RIPE | ASSIGNED PA | ● low |
| 213.24.160.96/27 | RTCOMM-NTI | RIPE | ASSIGNED PA | ● low |
| 213.24.160.128/25 | RTCOMM-NTI | RIPE | ASSIGNED PA | ● low |
| 213.24.170.0/23 | RTCOMM-NTI | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
Possible discrepancies (1)
These blocks are registered to RTCOMM-NTI but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 213.24.170.0/23 /23 | authorized for AS12389 — PJSC Rostelecom |
NIC Handles
AS8342-MNT
DUMY-RIPE
DUMY-RIPE