Rostelecom connects 1.2 million cameras to its cloud video platform
Rostelecom reports 1.2 million connected cameras and roughly 175 TB of video uploaded per hour. We examine scale and security considerations.
Contents
On 27 July 2026, Rostelecom said that 1.2 million cameras were connected to its home cloud video-surveillance platform. The company reports that approximately 175 TB of recordings enters the cloud every hour. Archive availability depends on the plan and ranges from seven days to one month.
More than half of customers, 53%, place cameras at country homes or in private yards. Rostelecom also highlights demand for Wi-Fi devices with night vision and motion detection, and for rotating 4G cameras at locations without fixed internet access.
What 175 TB per hour says about the platform
Even without internal codec and bitrate data, the figure indicates the workload class. The platform must continuously accept many parallel streams, enforce access rights, store data, serve live and archived views, and delete records according to retention policy.
Important architectural capabilities include:
- horizontal scaling of video ingest;
- separation of live-view and archive workloads;
- back-pressure handling over unstable mobile links;
- geographic redundancy for metadata and recordings;
- monitoring of camera-to-cloud latency;
- verifiable deletion after retention expires.
Storage availability alone does not make the service available. A user also depends on the access network, identity service, device catalogue, application and temporary-link service. The full user journey therefore needs to be measured. Our guide to SLIs, SLOs and error budgets explains this approach.
Security matters more than feature count
Rostelecom says recordings are encrypted and stored in its protected cloud. The owner manages access by creating another account or sharing a live-view link. Those are useful controls, but a business assessment requires current documentation and contractual detail.
Questions to clarify include:
- Is the stream encrypted from the camera, and where does the protected session terminate?
- How are shared links revoked, and do they expire?
- Is multi-factor authentication supported?
- Are views, downloads and configuration changes logged?
- Where are primary and backup copies stored?
- What happens to data when a camera or account is deleted?
- Who has administrative access to the archive?
Corporate deployments may also require role-based access, SIEM integration, audit exports and a formal retention schedule. The recovery layer is covered in our guide to backup and fault tolerance.
Practical conclusion
The figures show that cloud video surveillance has become an infrastructure service in its own right rather than a minor camera feature. A similar architecture can help businesses connect sites quickly and manage them centrally, but selection should be based on privacy, connectivity, retention and incident-investigation requirements.
Source: the official Rostelecom press release dated 27 July 2026; the original source is linked in the article metadata.
Primary source: Rostelecom: 1.2 million home video-surveillance cameras
