How good is JIO FIBER for gaming(Quality Check). Planning to upgrade(NEW UNLIMITED Plans).

Messages
130
Location
Ranchi
ISP
BSNL
why is there hard cap bro in jio fiber..in 399 plan max it reaches d/l speed 27-28 ?so kanjus jio..atleast 30-35 they should have given i.e 4mBps..
 
Messages
137
Location
NA
ISP
Jio GigaFiber
@Siddharth070999 speedtest websites aren’t an absolutely accurate measure of testing your maximum bandwidth. Try downloading from a direct link off a good server on LAN.
 
Messages
4
Location
Dhanbad
ISP
Jio Fiber
@kkapoorr Network Address Translation. Basically this is needed if you don't have a public IPv4 address. In Jio, you have a private IPv4 address. It means your IP address is an address in Jio's internal network, and not visible to the internet. People from outside can't reach you with just IP address, because this public IP address is shared by many people in Jio's internal network. NAT tells IP packets coming from internet which internal IP address to go to, since you're not directly visible outside. It's like you're permanently living in a hotel room, courier from outside comes only till reception desk with your name. Hotel staff (like NAT) does the job of delivering the packet till your room. The sender didn't know your room number, only hotel name. The problem comes in peer to peer applications like some games like FIFA, where direct IP connection is needed. Open NAT means you're directly accessible from outside without intermediaries like the hotel staff. This NAT used at level of ISPs is called carrier grade NAT (CGNAT). Another NAT that happens is in your home network. The packets come till your router which sends them to right devices. This one is fixed by forwarding ports since you have the router access, but CGNAT happens at ISP's router, you can't do much.

In Jio you have a private IPv4 (CGNAT) and public IPv6. So if the application is using IPv4, it will see NAT type strict, if it is using IPv6, it will see an open NAT.
Can I do anything to improve my ping in games like valorant(+100ms) and CSGO?
 
Messages
9
Location
India
ISP
JIO GIGA FIBER
Bro... Listen to me.... I have been a JIO FIBER user for more than a year now. If you want a WiFi for just normal day to day use, its excellent. But if you are planning on getting JIO FIBER for gaming.... Just don't. It is literally THE WORST ISP for gaming. The router has something known as DOUBLE NAT which will not let you forward ports nor enable UPnP. Both of those functions are really important if youre a gamer. I would recommend you to get an AirTel connection if you want to play games.

I play on PS4
Fortnite: Middle East Servers - 60-80ms
COD MW/Warzone: Sometimes 80-100ms but mostly 200ms+
Rocket League: SE Maritime Servers - 80-105ms and Middle East Servers 190ms+

Something seems to be wrong with their routing I guess. I really don't know whats wrong to be getting these kinds of absurd pings....

On CMD, when I ping 8.8.8.8 (GOOGLE DNS)... I get the following results...
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 39ms, Average = 37ms

Whereas in AirTel, the average ping is around 15-20ms.
I am getting these results on ping 8.8.8.8
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms


did they fixed double nat?
 
Messages
36
Location
Kolkata, India
ISP
Jio Fiber
Ping results to '8.8.8.8 (IPv4)'

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=27ms TTL=114
Reply from 8.8.8.8: bytes=32 time=26ms TTL=114
Reply from 8.8.8.8: bytes=32 time=27ms TTL=114
Reply from 8.8.8.8: bytes=32 time=26ms TTL=114

Ping results to '8.8.8.8 (IPv6)'

Pinging 2001:4860:4860::8888 with 32 bytes of data:
Reply from 2001:4860:4860::8888: time=31ms
Reply from 2001:4860:4860::8888: time=31ms
Reply from 2001:4860:4860::8888: time=31ms
Reply from 2001:4860:4860::8888: time=31ms

Ping results to '1.1.1.1 (IPv4)'

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=46ms TTL=55
Reply from 1.1.1.1: bytes=32 time=46ms TTL=55
Reply from 1.1.1.1: bytes=32 time=46ms TTL=55
Reply from 1.1.1.1: bytes=32 time=46ms TTL=55

Ping results to '1.1.1.1 (IPv6)'

Pinging 2606:4700:4700::1111 with 32 bytes of data:
Reply from 2606:4700:4700::1111: time=2ms
Reply from 2606:4700:4700::1111: time=1ms
Reply from 2606:4700:4700::1111: time=2ms
Reply from 2606:4700:4700::1111: time=2ms