Jio users report network issues, company says fix enroute

Several Reliance Jio users are complaining of network issues across the country. Users have taken to Twitter for complaining.

Reliance Jio network was reportedly down around 11 am in several parts of the country.  (Bloomberg)

Reliance Jio users are complaining of network issues on the social media. The Jio network is reportedly down in several parts of the country and subscribers are unable to make calls. The company is yet to come up with an official announcement regarding this.

Several users took to Downdetector to report issues related to Jio's network around 11 am today. However, as of now, the spike has gone down and Jio's network seems to working fine. We were able to make calls and access Internet from our Jio connection in Noida.

Jio network down in most cities

Based on all the complaints noted on Twitter, it seems that the problem has been present in several parts of the country, especially in the metro cities of Delhi, Mumbai, Bengaluru, Chennai, as well as in cities like Raipur and Indore. 

The Twitter handle for JioCare is currently replying to all users, asking them to send their numbers for further investigation. The company ahs so far stated the following, "We are currently experiencing connectivity issues in your location. Our team is working on the same and services will be restored as soon as possible."

It's 11.44 NO NETWORK #Jiodown @reliancejio
RAIPUR, CHHATTISGARH pic.twitter.com/ChuOvethwr

— Akshay sharma (@Akshays54628819) October 6, 2021

Based on the latest data from Downdetector, it seems that the problem is getting solved but there's still a substantial number of users still claiming network down complaints. The issue seems to have started around 9 am this morning and peaked at 11 am.

Jio's network issue comes right on the tail of the mega service issue that plagues all of Facebook owned companies. Two days ago, Facebook, Instagram and WhatsApp services were down for almost six hours at a stretch. Facebook later reported that the issue arose out of a faulty configuration on their servers, which was fixed later.