Full Report
Russia’s communications regulator, Roskomnadzor, confirmed Tuesday that it has deliberately “slowed down” the app, which has nearly 90 million local users, citing the company’s failure to comply with Russian law.
Analysis Summary
# Regulation/Compliance: Russian Data Content and Security Mandate Enforcement
## Overview
This summary addresses the regulatory action taken by Roskomnadzor against Telegram due to the platform's alleged failure to comply with Russian laws pertaining to content removal (specifically regarding "extremist" activity and pornography) and previous requirements related to data and encryption access (the 2018 encryption key demand). The enforcement action taken is network throttling ("deliberately slowed down").
## Key Details
- **Issuing Authority:** Roskomnadzor (Russia’s communications regulator), supported by Moscow courts.
- **Effective Date:** Enforcement action (throttling) confirmed "Tuesday" preceding the article date (February 11th, 2026). Previous content-related case filings started at the beginning of 2026.
- **Jurisdiction:** Russian Federation.
- **Status:** In Effect (Throttling is ongoing).
## Requirements
### Mandatory Requirements
1. **Content Removal Compliance:** Immediately delete specific content flagged by authorities, including material inciting "extremist" activity or containing prohibited pornography.
2. **Data/Encryption Access (Historical Context):** Comply with past judicial mandates, such as yielding encryption keys to the Federal Security Service (FSB) upon request (failure to do so previously resulted in a ban attempt).
3. **Call Restriction Compliance:** Adhere to regulations restricting the use of messaging features (like Telegram and WhatsApp calls) if authorities deem them frequently used for illegal recruitment (e.g., "sabotage and terrorist activities").
### Recommended Practices
1. **Proactive Content Moderation:** Implement robust internal mechanisms to swiftly identify and remove content matching Russian legal definitions of "extremist" material to preempt regulatory intervention.
2. **Engage in Dialogue:** Maintain open lines of communication with Roskomnadzor regarding compliance status, as Russia indicated they remain in contact with the company.
## Affected Organizations
- **Industries:** Telecommunications, Digital Messaging Platforms, Over-The-Top (OTT) Service Providers operating within Russia.
- **Organization Size:** Affects any platform with significant Russian user base (Telegram has nearly 90 million local users).
- **Geographic Scope:** Entities operating or accessible within the Russian Federation.
## Compliance Timeline
- **2018:** Initial demand for encryption keys; failure to comply resulted in a block order.
- **2020:** Block lifted after platform signaled willingness to cooperate on counter-terrorism/extremism.
- **August (Prior Year):** Roskomnadzor restricted calls due to fraud/terrorism concerns.
- **Start of 2026:** Moscow court opened seven cases against Telegram for alleged refusal to delete content.
- **"Tuesday" (Report Date):** Roskomnadzor began deliberate network throttling due to ongoing non-compliance.
- **Final deadline:** Compliance is required as long as alleged violations continue, as stated by the Kremlin spokesperson.
## Implementation Guidance
### Assessment Phase
- **Violation Catalog Review:** Immediately assess the seven specific court cases opened since the start of 2026 to identify the exact content categories driving the current enforcement action.
- **Content Policy Mapping:** Compare current platform content policies against specific Russian legal definitions of "extremist activity" and prohibited pornography.
### Implementation Phase
- **Execute Court Orders:** Comply immediately with demands related to the current seven cases to halt the network throttling.
- **Review Call Functions:** Verify moderation and monitoring processes for VOIP/calling features to ensure they are not facilitating activities flagged by Roskomnadzor.
### Validation Phase
- **Monitor Throttling Status:** Track key performance indicators (KPIs) related to application speed and connectivity within Russia to confirm the resumption of normal service levels following compliance actions.
- **Legal Review:** Obtain official confirmation or closure notices from Moscow courts regarding the resolved content cases.
## Technical Requirements
The required technical compliance shifts from specific infrastructure demands (like encryption keys in 2018) to **content accessibility and removal**.
1. **Content Deletion APIs/Mechanisms:** Develop or utilize mechanisms capable of instantly purging specific URLs or content based on Roskomnadzor/court directives.
2. **Traffic Prioritization/Bypass (if applicable):** If throttling is being applied via deep packet inspection (DPI) or bandwidth limits, the organization needs to determine if meeting content demands will automatically restore standard traffic routing.
## Penalties & Enforcement
- **Fines:** Telegram reportedly faces fines totaling **more than $820,000** across the seven opened cases.
- **Other Consequences:** Deliberate, widespread **network throttling** affecting nearly 90 million users, severely degrading service quality (slowdowns reported across nearly 15 regions). Potential for full blocking/banning, as occurred in 2018.
- **Enforcement:** Direct action by Roskomnadzor via throttling internet service providers (ISPs) affecting the specific application's traffic flow, backed by mandates from Moscow courts.
## Related Standards
- **Russian Federal Law on Information, Information Technologies and Information Protection (No. 149-FZ):** This broad legislation underpins the content removal and data handling responsibilities enforced by Roskomnadzor.
- **Laws Pertaining to Countering Extremism and Terrorism:** These laws govern the specific content categories leading to the current enforcement actions.
## Resources
- **Official Documentation:** (Note: Direct links to regulatory laws listed are withheld as per standard practice, but organizations should reference current Roskomnadzor guidance and relevant decisions from Moscow courts issued in early 2026.)
- **Guidance Documents:** Statements released by Roskomnadzor confirming the throttling action and referencing specific non-compliant content categories.
- **Tools:** Internet monitoring services (like Downdetector) are used by the public and analysts to validate the effectiveness of enforcement actions.
## Practical Recommendations
1. **Immediate Triage:** Prioritize resolving the content issues cited in the seven ongoing court cases to secure an immediate cessation of the network throttling.
2. **Risk/Benefit Analysis on Sovereignty:** For platforms operating in adversarial regulatory environments, critically assess the long-term viability of maintaining operations without adopting state-mandated surveillance capabilities (highlighted by founder Durov’s assertion that Moscow favors surveillance-ready "Max" app).
3. **Contingency Planning (Circumvention):** Be aware that throttling is an intermediary step; a full block remains a high risk, necessitating robust VPN/circumvention strategies for end-users if the conflict escalates further.
4. **Security Context Awareness:** Note the impact on critical services (e.g., Belgorod warnings regarding emergency communication disruption during wartime), indicating the regulatory compliance demands intersect directly with national security and operational continuity concerns.