Reliance Jio Fiber Pune users

  • Thread starter Thread starter Yatch
  • Start date Start date
  • Replies Replies 20
  • Views Views 3,651
Yatch

Yatch

Messages
162
Location
pune
ISP
JioFiber, Airtel Xstream fiber
Could you guys please tell what ping times you get to 8.8.8.8, 1.1.1.1, 3.6.0.0 (Amazon Mumbai server), and 15.184.0.253 (Amazon Middle east server)?
On my local ISP's I would get 5ms to these servers in Mumbai, but with Jio Fiber I am pinging a horrible 30ms+
I Ping around 25ms to Jio Bhopal server and 35ms to servers in Pune on speedtest which is so dumb.
I am currently in the trial period, hopefully I would be assigned a better IP address pool when the trial is over?
My wife has JioFiber in Kharghar and she pings 5ms to Google/ cloudfare DNS and AWS servers.
Jio's routeing is just ridiculous. I have emailed their customer care, which forwarded the issue to the technical team. It's been 9 days and I haven't herd from them since.
I will see if escalating this to PG portal would solve the problem.
I am also using ExpressVPN, but the pings dont get any better since my base ping to their VPN Mumbai server is a miserable 30ms+ thanks to Jio's routeing.
Thanks in advance
 
Where (which area) are you located in Pune?
 
Same for me as well, I am living in Kharadi. I checked with few of my friends, they are having the same speeds, more than 30+ms
 
Thanks for checking it out. Even on Ookla speed test, I am getting equal or better pings on Jio Bhopal/ Jio Ahemdabad/ Jio Lucknow/Jio Hydrabad/ Jio Chennai/Jio Bhubaneshwar as compared to Jio Navi Mumbai or Mumbai. Their routeing is just pathetic. Their customer care is even brain dead. Sometimes I wonder if they are AI bots with random name generator.

Source

Not relevant, but this is their setup on my terrace.

Source
 
Last edited by a moderator:
I would like to provide a quick update. Jio seems to now be using the Mumbai Gateway for Pune users, and the pings have improved noticeably.
The pings to 8.8.8.8/ 1.1.1.1/ AWS Mumbai (Valorant servers) are between 4ms to 8ms (previously 30+ms)
Latency to Middle east AWS servers is 38-40ms (previously 60+ms )and Singapore 56ms-60ms (previously 65+ms)
The Public IPV4 addresses previously were 49.36.44.xx/49.36.41.xx/49.36.43.xx
As of now my public IP is 49.36.108.xx. This is the Public IP address subnet for Jio Mumbai users.
I hope it stays this way and I don't get kicked back to the Nagpur gateway.
The browsing experience had been very poor for the past few days, and maybe due to numerous complaints Jio might have made the switch o Mumbai for Pune users. Could you guys pls confirm if you have a better ping to 8.8.8.8 now? Or maybe it's just in my neighborhood?
 

Guys, Jio fiber just contacted my housing society manager asking for permission to set up their equipment here. One of the members is interested in a connection. For those who have connectivity what exactly did they install in the society? Anybody from Pune East (Camp, etc) who can share their experience with Jio?
 
@Chip Jio started service in out society recently. I also see some boxes in building duct as seen in post #5 above. From those box, fiber optic cable is coming inside house and connected directly to Router (no converter needed in between).
 
@SVK ok thanks bro. I'll update this thread if this JF thing moves forward. It is similar to what Airtel and Tata Play have done in the buildings.

BTW how is the service. I ask because it seems to vary from city to city hence interested in Pune based user feedback. Also which part of Pune do you live in?
 
@Chip Jio service is so far good, using it for 3 months now. But I stay at other end of Pune (actually not even in Pune, its Pimpri).
 
@Lolita_Magnum did these tests straight from the ONT.


Middle East EC2 server

Code: 
traceroute to 15.184.0.253 (15.184.0.253), 30 hops max, 38 byte packets
 1  10.13.184.1 (10.13.184.1)  4.507 ms  1.828 ms  3.709 ms
 2  172.31.3.64 (172.31.3.64)  2.895 ms  172.31.3.60 (172.31.3.60)  2.458 ms  2.807 ms
 3  192.168.92.246 (192.168.92.246)  2.063 ms  192.168.92.244 (192.168.92.244)  2.065 ms  2.367 ms
 4  172.26.106.117 (172.26.106.117)  1.463 ms  1.607 ms  2.369 ms
 5  172.26.106.98 (172.26.106.98)  3.326 ms  172.26.106.99 (172.26.106.99)  2.419 ms  172.26.106.98 (172.26.106.98)  2.640 ms
 6  192.168.92.166 (192.168.92.166)  2.567 ms  192.168.92.162 (192.168.92.162)  2.697 ms  192.168.92.160 (192.168.92.160)  2.398 ms
 7  192.168.92.167 (192.168.92.167)  3.652 ms  192.168.92.165 (192.168.92.165)  3.097 ms  192.168.92.161 (192.168.92.161)  2.655 ms
 8  172.31.2.73 (172.31.2.73)  5.670 ms  6.182 ms  172.31.2.71 (172.31.2.71)  5.171 ms
 9  99.83.67.30 (99.83.67.30)  6.102 ms  19.174 ms  99.82.178.202 (99.82.178.202)  5.145 ms
10  52.95.65.213 (52.95.65.213)  6.203 ms  52.95.65.215 (52.95.65.215)  5.967 ms  52.95.67.249 (52.95.67.249)  6.221 ms
11  *  *  *
12  52.95.65.85 (52.95.65.85)  5.057 ms  52.95.65.43 (52.95.65.43)  6.131 ms  52.95.65.89 (52.95.65.89)  5.557 ms
13  52.95.67.103 (52.95.67.103)  5.545 ms  52.95.67.31 (52.95.67.31)  5.539 ms  52.95.67.55 (52.95.67.55)  5.057 ms
14  *  *  *
15  *  *  *
16  *  *  *
17  *  *  *
18  *  *  *
19  *  *  *
20  *  *  *
21  *  *  *
22  *  *  *
23  ec2-15-184-0-253.me-south-1.compute.amazonaws.com (15.184.0.253)  40.920 ms  40.911 ms  41.790 ms


Singapore EC2 server
Code: 
traceroute to 3.0.0.9 (3.0.0.9), 30 hops max, 38 byte packets
 1  10.13.184.1 (10.13.184.1)  1.435 ms  1.628 ms  2.252 ms
 2  172.31.3.60 (172.31.3.60)  2.468 ms  3.151 ms  2.006 ms
 3  192.168.92.242 (192.168.92.242)  2.263 ms  192.168.92.246 (192.168.92.246)  2.674 ms  192.168.92.244 (192.168.92.244)  2.096 ms
 4  172.26.106.117 (172.26.106.117)  1.712 ms  2.455 ms  2.410 ms
 5  172.26.106.99 (172.26.106.99)  2.600 ms  172.26.106.98 (172.26.106.98)  3.130 ms  3.660 ms
 6  192.168.92.166 (192.168.92.166)  2.184 ms  192.168.92.164 (192.168.92.164)  3.151 ms  192.168.92.166 (192.168.92.166)  2.562 ms
 7  192.168.92.161 (192.168.92.161)  3.130 ms  192.168.92.167 (192.168.92.167)  2.608 ms  3.114 ms
 8  172.31.3.25 (172.31.3.25)  23.106 ms  22.253 ms  22.775 ms
 9  103.198.140.170 (103.198.140.170)  22.540 ms  22.873 ms  103.198.140.64 (103.198.140.64)  23.125 ms
10  49.45.4.86 (49.45.4.86)  54.279 ms  103.198.140.17 (103.198.140.17)  54.752 ms  103.198.140.89 (103.198.140.89)  54.722 ms
11  99.82.179.24 (99.82.179.24)  53.543 ms  56.846 ms  103.198.140.15 (103.198.140.15)  55.707 ms
12  *  *  99.82.179.24 (99.82.179.24)  53.429 ms
13  *  *  *
14  *  *  *
15  *  *  *
16  *  *  *
17  *  *  *
18  *  *  *
19  *  *  *
20  *  *  *
21  *  *  *
22  *  *  *
23  *  ec2-3-0-0-9.ap-southeast-1.compute.amazonaws.com (3.0.0.9)  56.257 ms  55.456 ms


EC2 Mumbai server
traceroute to 13.232.0.253 (13.232.0.253), 30 hops max, 38 byte packets
1 10.13.184.1 (10.13.184.1) 1.506 ms 1.413 ms 1.150 ms
2 172.31.3.60 (172.31.3.60) 2.302 ms 172.31.3.64 (172.31.3.64) 2.170 ms 3.191 ms
3 192.168.92.246 (192.168.92.246) 2.083 ms 192.168.92.242 (192.168.92.242) 2.587 ms 2.212 ms
4 172.26.106.117 (172.26.106.117) 1.628 ms 1.615 ms 2.283 ms
5 172.26.106.98 (172.26.106.98) 3.289 ms 172.26.106.99 (172.26.106.99) 2.672 ms 3.123 ms
6 192.168.92.160 (192.168.92.160) 2.718 ms 2.653 ms 192.168.92.164 (192.168.92.164) 2.701 ms
7 192.168.92.163 (192.168.92.163) 3.056 ms 192.168.92.161 (192.168.92.161) 2.506 ms 192.168.92.163 (192.168.92.163) 3.251 ms
8 172.31.2.71 (172.31.2.71) 5.122 ms 172.31.2.73 (172.31.2.73) 5.631 ms 172.31.2.71 (172.31.2.71) 6.134 ms
9 99.82.178.202 (99.82.178.202) 4.591 ms 13.407 ms 99.83.67.30 (99.83.67.30) 5.952 ms
10 52.95.65.217 (52.95.65.217) 6.089 ms 52.95.64.121 (52.95.64.121) 5.664 ms 52.95.64.119 (52.95.64.119) 6.175 ms
11 52.95.64.140 (52.95.64.140) 5.579 ms 52.95.64.166 (52.95.64.166) 5.135 ms 52.95.64.254 (52.95.64.254) 5.081 ms
12 52.95.64.207 (52.95.64.207) 6.127 ms 52.95.64.187 (52.95.64.187) 7.191 ms 52.95.64.131 (52.95.64.131) 7.620 ms
13 52.95.67.129 (52.95.67.129) 5.646 ms 52.95.66.85 (52.95.66.85) 10.115 ms 52.95.66.173 (52.95.66.173) 7.135 ms
14 99.83.76.88 (99.83.76.88) 6.083 ms 99.83.76.70 (99.83.76.70) 6.675 ms 99.83.76.92 (99.83.76.92) 8.014 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 ec2-13-232-0-253.ap-south-1.compute.amazonaws.com (13.232.0.253) 5.886 ms * *
 
@Chip The connection quality is good, but in case of problems resolution takes time, the customer service is not so responsive. There is no OTP system for problem resolution. In case you miss the call from the service engineer, he just closes your case and moves on to the next complaint, and you have to raise a complaint again. But downtimes are rare.

Jio DNS Servers are slow, Especially their IPv6 DNS Servers, the browser mostly reverts to Ipv4. Apart from changing the DNS on your device, you can change the DNS Servers on the ONT as well (might require a restart), dint check if it affects calling.

Jio blocks Cloudflare WARP VPN. I can use Cloudflare teams, but for many users it does not work.
 
@Yatch thanks for the feedback. Anyways this will be an option to residents if they do install their fibre in the colony.
 
So, JF received permission from the colony to install their fibre and related gear. Work will start end April.
 

Top