PJSC Rostelecom
CTC-Kubinka-NF
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 208553946 |
| 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 (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 89.109.240.0/24 | CTC-Kubinka-NF | RIPE | ASSIGNED PA | ● low |
| 89.109.241.0/24 | CTC-Kubinka-NF | RIPE | ASSIGNED PA | ● low |
| 95.73.216.0/21 | CTC-Kubinka-NF | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “CTC Kubinka” — 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.
- CTC-Kubinka-PPPoE 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.
- Kubinka Pppoe via PJSC Rostelecom sub-allocation
- Kubinka-Nedvigimost via Limited liability company "New Line" sub-allocation
- Administraciya-gorodskogo-poseleniya-Kubinka via Limited liability company "New Line" sub-allocation
- kubinka-net sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
RPKI-inferred operator
PJSC Rostelecom
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
ROSTELECOM-MNT