Telegram fails on Movistar and O2 fiber in some areas

Telegram down on Movistar and O2 fiber while mobile works

The messaging app Telegram stopped working normally for a portion of Movistar fiber customers and operators riding on its network, such as O2. Affected users describe an annoying pattern: the app stays empty, synchronization with the phone breaks, and if one tries to reinstall it, the download also fails. The detail that confuses everyone is that from the same company's mobile network, the service runs smoothly, and on networks of operators with their own infrastructure —Vodafone, Orange, Digi, Euskaltel, or Jazztel— there is no problem at all.

The conclusion is that the fault is not in the application, but somewhere in the fixed network. And it does not affect all customers equally: the incident seems concentrated by region, pointing to specific nodes or interconnection centers. Movistar has not responded to requests for information, according to material circulated about the case.

Why does Telegram work on mobile but not on fiber?

The most repeated diagnosis is an involuntary block in fiber routing. A single operator's mobile and fixed networks do not necessarily share the same paths to Telegram servers, so a badly applied filter in a peering node can knock out the service in one region and leave the rest intact. This irregular behavior —some users yes, others no, depending on where they live— is the usual signature of an infrastructure problem, not a corporate decision.

Some argue it is a deliberate block. The argument has some traction: Telegram was almost blocked in Spain for hosting channels distributing audiovisual content protected by copyright, exactly the type of content operators sell via subscription. The suspicion is reasonable. The problem is that it is also a self-inflicted wound: cutting a mass messaging app angers the customer and pushes them to look at competitor offers.

The precedent of Telegram blocks in Spain

The shadow of censorship looms over any service outage, especially in a country where Telegram itself has been under judicial scrutiny due to how some use its channels. The difference between a block and a breakdown is invisible to the user: in both cases, the app does not load. The only reliable clue is the geographic pattern and the asymmetry between mobile and fiber.

In practice, affected users have resorted to emergency solutions. The most cited is activating an anonymous proxy within the app itself, which bypasses the problematic node and restores connection without changing companies. Others have opted for more drastic measures: switching operators, with Digi being a recurrent destination due to price and independence from Telefónica's network.

What does Movistar risk with the Telegram block?

The fruta cost is evident. An operator controlling the infrastructure on which third parties also provide service —O2 is the clearest case— drags those third parties into any incident. If the fault is technical, the solution involves identifying the node and correcting it. If it is deliberate, the commercial calculation is hard to sustain: messaging is now a basic utility, not an extra.

The official narrative, for now, does not exist. Without confirmation or denial, theories fill the void. And in that area, the most cited is not the copyright block theory, but that of a technical test prior to a broader cut. None of this is proven, but the absence of explanation is, in itself, data.

---

The issue remains where it started: some customers without service, a company without explanation, and an app that works or not depending on where traffic exits. Until there is an official response, each affected user will have to decide whether to wait, use a proxy, or switch operators.