Internet services shut in held Kashmir ahead of Burhan Wani's death anniversary

Separatist groups have called for a strike on July 8 to pay homage to those killed in action by Indian forces


News Desk July 07, 2017
Indian Police tell internet service providers to suspend their services amid first death anniversary of Burhan Wani. PHOTO: AFP

SRINAGAR: Indian Police on Thursday told internet service providers in held Kashmir to completely suspend services till further orders in lightof the first death anniversary of separatist leader Burhan Muzaffar Wani this weekend.

According to NDTV, Inspector General of Police Kashmir Munir Ahmad Khan on Thursday issued an order to various lease line internet service providers in the disputed valley to block all social media websites. "In view of the apprehensions of misuse of internet services by anti-national elements, which is likely to cause deterioration in law and order situation, you are directed to block all social media sites," it said.

Indian troops kill 11, including Burhan Wani's successor, in IOK

Wani's killing by Indian forces during an encounter on July 8, 2016, had triggered massive protests and prolonged curfews across the region. Several Kashmiris were killed and thousands of others were injured during bloody clashes with Indian forces.

Separatist groups have called for a strike on July 8 to pay homage to those killed in action by Indian forces against stone-pelting Kashmiri protesters.

A dangerous new phase of Kashmir conflict

Meanwhile, security has been beefed up in the Himalayan region, especially in South Kashmir districts. Indian Police and security forces have intensified area domination to prevent assembly of people in Wani's native village in Tral, said the report.

Indian forces on May 24 killed eleven Kashmiris, including Sabzar Ahmad Bhat the successor of Wani, in Kashmir.

This story was originally published on NDTV.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ