How Telegram, using Google and Amazon's cloud services, humiliated and outmaneuvered Russia's state telecom regulator, Roskomnadzor, and survived the ban
Isabelle Khurshudyan / Washington Post :
Context & Ripple Effects
The story closes a two-year arc that began when Telegram moved its infrastructure onto AWS and Google Cloud and Roskomnadzor responded by blacklisting 1.8 million Amazon and Google IP addresses — a move that knocked out unrelated Russian services running on the same clouds while Telegram kept routing traffic. The Washington Post piece is the retrospective on how that cat-and-mouse game ended with the ban failing.
What makes the outcome notable is who else tried the same trick: weeks into the episode, Amazon told Signal it had to stop anti-censorship domain-fronting or lose access to AWS — so Telegram survived where a smaller peer was squeezed out. By 2022, analysts judged another ban attempt technically difficult for an app serving 40M+ Russian users, and the app's survival positioned it as a dominant wartime news channel.
First-order effects
- Roskomnadzor's IP-blocking strategy directly harmed Russian users of ordinary cloud-hosted services far beyond Telegram, since 1.8M shared Amazon and Google addresses went dark — the regulator paid a domestic cost for every escalation while Telegram re-routed around each block.
- Amazon and Google found themselves cast as de facto arbiters of whether a state censorship order succeeded or failed, without ever taking a public position on it.
Second-order effects
- Cloud providers' tolerance threshold became the decisive variable: Amazon's warning to Signal showed the platforms would accommodate evasion at one customer's scale but not another's, making provider goodwill a strategic dependency for any anti-censorship service.
- The failure taught Roskomnadzor that blocking foreign-shared infrastructure is self-inflicted damage, shifting future enforcement toward tools aimed at the network itself rather than at individual apps.
Third-order effects
- If states cannot censor services hidden inside hyperscaler infrastructure, the pressure moves toward national control of traffic and domestic alternatives — the sovereignty push visible in later attempts to restrict Telegram despite its 40M+ Russian users.
- A messenger that survives by being uncensorable inherits the governance vacuum that creates: the same hands-off architecture later turned Telegram into a key Ukraine-war news channel that coverage has flagged as a misinformation vector.
The trend: State internet censorship is colliding with the reality that modern services live on a few foreign clouds, pushing regulators toward network-level sovereignty controls they can actually enforce.