PJSC Rostelecom
TO
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 206 blocks across 56 clusters |
| Cluster ID | 206389169 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 188.128.121.112/29 | TO_Company | RIPE | ASSIGNED PA | ● low |
| 2a14:67c2:8e3::/48 | TO | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “TO” — 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.
- To_ERs_logically_close_to_BL-BR 88 blocks
- To_ERs_logically_close_to_BD-BR 13 blocks
- TO-20080305 13 blocks
- To_ERs_logically_close_to_MK-BR 13 blocks
- TO_TRANSIT 12 blocks
- TO_3560_L3_AVAYA_CLOSET 5 blocks
- TO-THE-NEW-PRIVATE-LIMITED 3 blocks
- TO-OCHA-ORG 3 blocks
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
ROSTELECOM-MNT
TIANJIN-JIANRONGWANGLUO-MNT