Rostelekom
Registry
Cluster stats
| Netblocks | 6 |
| All fragments | 27 blocks across 10 clusters |
| Cluster ID | 204549654 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-13
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 95.167.3.200/30 | Rostelekom | RIPE | ASSIGNED PA | ● low |
| 95.167.44.4/30 | Rostelekom | RIPE | ASSIGNED PA | ● low |
| 95.167.44.32/30 | Rostelekom | RIPE | ASSIGNED PA | ● low |
| 95.167.75.156/30 | Rostelekom | RIPE | ASSIGNED PA | ● low |
| 95.167.75.220/30 | Rostelekom | RIPE | ASSIGNED PA | ● low |
| 212.15.116.0/26 | rostelekom-net | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “Rostelekom” — 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.
- Rostelekom_UF_TU-2 6 blocks
- Rostelekom_CF 4 blocks
- Rostelekom_UF_TU-5 3 blocks
- Rostelekom_UF_TU-1 3 blocks
- RosTeleKom_ZAO 1 blocks
- Rostelekom_UF_TU-3 1 blocks
- Rostelekom_Juzhnyj_Filial_TU-1 1 blocks
- Rostelekom_Sibirskij_filial_TU-3 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.
- Rostelekom_Sibirskij_filial_TU-3 via PJSC Rostelecom sub-allocation
- Centralnyj_filial__Rostelekom via PJSC Rostelecom sub-allocation
- Rostelekom_Juzhnyj_Filial_TU-1 via PJSC Rostelecom sub-allocation
- Tsentralnyy_filial__Rostelekom via PJSC Rostelecom sub-allocation
- Rostelekom_UF_TU-3 via PJSC Rostelecom sub-allocation
- ROSTELEKOM-FSO-LAN via PJSC MegaFon sub-allocation
- Ros Tele Kom ZAO via PJSC Rostelecom sub-allocation
Network trust
what's this?
RPKI hygiene: B
how networks compare →
83.3%
of checked blocks have valid RPKI ROA coverage
(5 of 6)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
ROSTELECOM-MNT
cnt-mnt