Pavel Durov’s latest accusation has pushed a technical routing issue into the center of a global public dispute. The Telegram founder claimed that Reliance was disrupting access to Telegram for users outside India through BGP hijacking, a routing technique that can misdirect internet traffic by advertising false paths. Reliance Jio denied any involvement and said it was not part of any such incident. The controversy is unfolding while Telegram also faces temporary restrictions in India over an exam fraud investigation.

For most users, the phrase BGP hijacking sounds obscure. In reality, it describes one of the internet’s most sensitive routing failures. It can cause traffic to go to the wrong place, slow down access, or even block services entirely. That is why the dispute matters beyond Telegram. It touches on internet trust, network governance, corporate accountability, and the growing tension between platform access and national regulation.

What Pavel Durov Alleged

Durov said on X that Reliance was sabotaging Telegram access for millions of users outside India, including in the UAE, through what he called a rogue method known as BGP hijacking. He also suggested the disruption could be part of a wider competitive conflict and tied the allegation to Meta, which owns WhatsApp, though those claims remain unproven and were presented by him as suspicion rather than evidence. ThePrint and India Today both reported that he framed the issue as intentional and repeated the claim that multiple reports had been ignored.

That allegation quickly escalated because it was not limited to India’s domestic network problem. Durov said the access issue affected users abroad, which raised the stakes from a local service dispute to a broader routing integrity controversy. India Today reported that he described the event as a possible competitive war, while ThePrint noted that Telegram had already taken the Indian government to court over the temporary block.

The context matters. India temporarily blocked Telegram until June 22, 2026, after authorities said the app was used in connection with cheating networks tied to the National Eligibility cum Entrance Test, or NEET, and the government also directed Telegram to disable its message editing feature until June 30 over misinformation concerns. Reuters reported that Durov criticized the ban as punishing ordinary users, while the government said it was acting to protect exam integrity.

Why BGP Hijacking Matters

BGP, or Border Gateway Protocol, is the routing system that helps the internet decide where traffic should go. Cloudflare explains that BGP hijacking happens when someone falsely announces ownership of IP prefixes they do not control, causing traffic to be rerouted. In plain terms, it is like changing road signs so data ends up on the wrong road. That is why routing errors can affect reachability, speed, security, and trust all at once.

Business Standard’s technical explanation is useful here because it shows how the mechanism works in practice. It says a hijack can occur when a network advertises a route it should not be advertising, and other networks accept that claim because BGP is built around trust between autonomous systems. That trust model is efficient, but it also makes the system vulnerable when one network acts maliciously or misconfigures its routes.

This is why the allegation drew immediate attention from network engineers as well as tech watchers. APNIC has noted that BGP hijacking has long been one of the internet’s persistent security threats, and that detection and protection are still uneven across the global routing ecosystem. In other words, this is not a theoretical weakness. It is a known structural problem that keeps reappearing in different forms.

The risk is not only interruption. Cloudflare notes that traffic can be monitored, intercepted, blackholed, or redirected to fake destinations when routes are hijacked. That makes BGP security relevant to messaging apps, banks, cloud services, media platforms, and any business that depends on always-on connectivity. The Telegram dispute is therefore part of a much larger internet resilience conversation.

Reliance’s Response And The India Backdrop

Reliance Jio rejected Durov’s accusation. India Today reported that the company said it was not involved in any BGP hijacking incident and denied any BGP route misconfiguration. The company also said it follows global internet routing best practices and standards of reliability, security, and transparency. Economic Times carried a similar denial, emphasizing that Jio said there was no manipulation of its BGP routes.

That denial is important because the allegation was highly specific. Durov did not simply claim poor service or congestion. He named a routing method, named the company, and alleged intentional disruption. But the public evidence available so far, based on reporting from India Today and Business Standard, shows a dispute between accusation and rebuttal rather than a verified finding of wrongdoing.

The India backdrop also helps explain why the story spread so quickly. Reuters reported that the government’s temporary Telegram block followed concerns about exam fraud and leaked papers, while the platform’s critics argued the ban may penalize ordinary users more than the bad actors behind the leaks. Durov has used that same argument to say broad restrictions do little to stop abuse, since people behind leaks can simply move elsewhere.

What makes the dispute especially sensitive is that it merges three different layers of conflict. There is the public safety layer, because authorities want to stop exam fraud and misleading content. There is the platform layer, because Telegram is defending its users and access model. And there is the infrastructure layer, because routing allegations can imply far more than a local moderation issue. Once those layers overlap, the story stops being about one app and becomes about the rules of the internet itself.

What The Dispute Means For Telegram And The Internet

Even if the dispute remains unproven, it reveals how fragile user trust can become when access problems, political pressure, and network engineering collide. Telegram depends on scale and reliability. If users believe access is unstable or manipulated, the app loses credibility whether the cause is regulation, routing errors, or competitive pressure. That is why Durov’s choice to frame the issue as BGP hijacking matters so much. The term itself signals a serious infrastructure-level threat.

The broader lesson is that online platforms can no longer treat routing security as a niche technical matter. As more public life moves onto messaging platforms, any disruption can become a political story, a business story, and a security story at the same time. APNIC and Cloudflare both show that BGP hijacking is not exotic. It is a known failure mode that needs monitoring, coordination, and better routing hygiene across providers.

For policymakers, the Telegram case is a reminder that platform governance should be precise. Broad bans and blunt enforcement can create collateral damage, especially in countries with large user bases and heavy reliance on messaging apps for work, education, and daily communication. For network operators, the case is a reminder that route validation and incident response are no longer optional extras. They are core elements of trust in the digital economy.

For Telegram, the episode is a reputational test. Durov has repeatedly positioned the company as a defender of user access and privacy, but the current dispute puts the platform under intense scrutiny from regulators, telecoms, and the public. Whether the issue is ultimately proven to be a routing problem, a misconfiguration, or something else entirely, the debate has already shown how quickly a technical allegation can become a global headline.

In the end, the phrase BGP hijacking is now doing more than describing a network event. It is shaping the political and commercial narrative around Telegram’s access problem. That makes this story bigger than one accusation. It is a case study in how fragile internet trust can become when routing, regulation, and rivalry all collide at once.