Google confirms some of its services, including Google Search, Gmail, and Android push notifications, continue to suffer outages in Russia amid Telegram ban
Context & Ripple Effects
This outage is the collateral damage of a censorship fight: after Telegram shifted parts of its infrastructure onto AWS and Google Cloud, Roskomnadzor responded by banning 1.8 million Amazon and Google IP addresses — a block so broad it swept up unrelated Google services. Google confirming that Search, Gmail, and Android push notifications are still degraded six days in shows the ban is not a blip but an ongoing standoff.
The episode sits in a longer arc of Google-Russia friction, from the company's Crimea cutoff of AdWords, AdSense, and Google Play in 2015 to its eventual halt of ad sales in Russia in 2022. What makes the Telegram case distinct is that the damage is self-inflicted by the regulator: blocking a messaging app means degrading the very Western platforms ordinary Russians depend on daily.
First-order effects
- Russian users of Gmail, Google Search, and any app relying on Android push notifications face intermittent or broken service right now, with no fix available until either Google or Roskomnadzor changes course.
Second-order effects
- Google is forced into an uncomfortable position: absorbing the cost of another state's censorship of Telegram, or pulling infrastructure out of Russia entirely — while other cloud-dependent services hosted on the banned IP ranges face the same squeeze.
Third-order effects
- If the pattern holds — and Telegram ultimately outmaneuvered Roskomnadzor by riding US clouds — IP-range bans prove a blunt instrument against distributed infrastructure, pushing censors toward deeper packet inspection and pressuring states to demand local hosting they can switch off unilaterally.
The trend: State censorship built on IP blocking is colliding with shared cloud infrastructure, making collateral outages of major consumer services an inherent feature of national firewalls.