In a move that has stirred controversy and sparked heated debate, India has blocked the Instagram accounts of Pakistani cricket stars Babar Azam, Shaheen Shah Afridi, and Mohammad Rizwan from being accessed within its borders. This step comes as part of India’s reaction to the tragic Pahalgam terrorist attack, which claimed the lives of 26 civilians in Jammu and Kashmir.
Indian users trying to view these profiles are now met with a message saying: “Account not available in India. This is because we complied with a legal request to restrict this content.” The action follows a similar restriction recently imposed on the Instagram account of Olympic medalist Arshad Nadeem, raising questions about the widening scope of digital censorship tied to geopolitical tensions. (Read more about the previous ban here)
The government has not officially stated why these specific accounts were targeted, but sources suggest it's part of a broader crackdown on content perceived to support or represent Pakistan in light of the attack. Alongside the Instagram bans, India has also taken down 16 Pakistani YouTube channels, accusing them of spreading misinformation and anti-India propaganda. (Click here to see the full list of banned channels)
These measures have triggered mixed responses on social media. While some Indians applaud the move as a stand against terrorism and a show of national unity, others argue that it punishes sports figures who are not involved in politics or violence. The bans raise an important question about whether digital actions against athletes contribute to national security—or blur the line between politics and sport.
As tensions between India and Pakistan continue to play out not only on the battlefield and in diplomacy, but also on social media platforms, these bans mark a significant chapter in how nations may choose to respond digitally to real-world events. Whether these blocks are temporary or the beginning of a longer digital divide remains to be seen. (Click here to follow the latest updates on this story)


0 Comments