How is the latency to Europe servers on Jio ?

  • Thread starter Thread starter Lousyaim
  • Start date Start date
  • Replies Replies 22
  • Views Views 4,918
Messages
22
Location
NA
I am looking forward to take Jio Fiber soon but want to know from the existing users about the ping they get in Europe servers ?
Here are some of the server IPs,
52.59.121.244
217.147.89.101
I would be grateful if you guys can let me know the ping of these IPs.
 
sayan@awemonk:~$ ping 52.59.121.244
PING 52.59.121.244 (52.59.121.244) 56(84) bytes of data.
64 bytes from 52.59.121.244: icmp_seq=1 ttl=42 time=170 ms
64 bytes from 52.59.121.244: icmp_seq=2 ttl=42 time=167 ms
64 bytes from 52.59.121.244: icmp_seq=3 ttl=42 time=170 ms
64 bytes from 52.59.121.244: icmp_seq=4 ttl=42 time=167 ms
^C
--- 52.59.121.244 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3011ms
rtt min/avg/max/mdev = 166.744/168.542/170.365/1.744 ms
sayan@awemonk:~$ ping 217.147.89.101
PING 217.147.89.101 (217.147.89.101) 56(84) bytes of data.
64 bytes from 217.147.89.101: icmp_seq=1 ttl=109 time=158 ms
64 bytes from 217.147.89.101: icmp_seq=2 ttl=109 time=160 ms
64 bytes from 217.147.89.101: icmp_seq=3 ttl=109 time=159 ms
^C
from JioFiber
 
Upvote 0
From Jio Fiber in North India although keep in mind these pings are the worst for me in a long time, these will drop to 150-170ms soon enough I would consider those as typical but plan upto these pings below as well if you have latency sensitive use case
Pinging 52.59.121.244 with 32 bytes of data:
Reply from 52.59.121.244: bytes=32 time=188ms TTL=48
Reply from 52.59.121.244: bytes=32 time=200ms TTL=48
Reply from 52.59.121.244: bytes=32 time=244ms TTL=48
Reply from 52.59.121.244: bytes=32 time=168ms TTL=48
Reply from 52.59.121.244: bytes=32 time=187ms TTL=48
Reply from 52.59.121.244: bytes=32 time=214ms TTL=48
Reply from 52.59.121.244: bytes=32 time=173ms TTL=48
Reply from 52.59.121.244: bytes=32 time=191ms TTL=48
Reply from 52.59.121.244: bytes=32 time=201ms TTL=48
Reply from 52.59.121.244: bytes=32 time=172ms TTL=48
Reply from 52.59.121.244: bytes=32 time=168ms TTL=48
Reply from 52.59.121.244: bytes=32 time=171ms TTL=48
Reply from 52.59.121.244: bytes=32 time=213ms TTL=48
Reply from 52.59.121.244: bytes=32 time=171ms TTL=48

Ping statistics for 52.59.121.244:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 244ms, Average = 190ms

Pinging 217.147.89.101 with 32 bytes of data:
Reply from 217.147.89.101: bytes=32 time=205ms TTL=111
Reply from 217.147.89.101: bytes=32 time=172ms TTL=111
Reply from 217.147.89.101: bytes=32 time=188ms TTL=111
Reply from 217.147.89.101: bytes=32 time=170ms TTL=111
Reply from 217.147.89.101: bytes=32 time=197ms TTL=111
Reply from 217.147.89.101: bytes=32 time=200ms TTL=111
Reply from 217.147.89.101: bytes=32 time=182ms TTL=111
Reply from 217.147.89.101: bytes=32 time=169ms TTL=111
Reply from 217.147.89.101: bytes=32 time=183ms TTL=111
Reply from 217.147.89.101: bytes=32 time=188ms TTL=111
Reply from 217.147.89.101: bytes=32 time=203ms TTL=111
Reply from 217.147.89.101: bytes=32 time=173ms TTL=111
Reply from 217.147.89.101: bytes=32 time=197ms TTL=111
Reply from 217.147.89.101: bytes=32 time=200ms TTL=111
Reply from 217.147.89.101: bytes=32 time=217ms TTL=111

Ping statistics for 217.147.89.101:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 169ms, Maximum = 217ms, Average = 189ms
 
Upvote 0
Code:
Pinging 52.59.121.244 with 32 bytes of data:
Reply from 52.59.121.244: bytes=32 time=152ms TTL=43
Reply from 52.59.121.244: bytes=32 time=152ms TTL=43
Reply from 52.59.121.244: bytes=32 time=153ms TTL=43
Reply from 52.59.121.244: bytes=32 time=152ms TTL=43

Ping statistics for 52.59.121.244:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 152ms, Maximum = 153ms, Average = 152ms


Pinging 217.147.89.101 with 32 bytes of data:
Reply from 217.147.89.101: bytes=32 time=150ms TTL=107
Reply from 217.147.89.101: bytes=32 time=148ms TTL=107
Reply from 217.147.89.101: bytes=32 time=149ms TTL=107
Reply from 217.147.89.101: bytes=32 time=148ms TTL=107

Ping statistics for 217.147.89.101:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 148ms, Maximum = 150ms, Average = 148ms
 
Upvote 0
Code:
Pinging 217.147.89.101 with 32 bytes of data:
Reply from 217.147.89.101: bytes=32 time=141ms TTL=109
Reply from 217.147.89.101: bytes=32 time=142ms TTL=109
Reply from 217.147.89.101: bytes=32 time=142ms TTL=109
Reply from 217.147.89.101: bytes=32 time=141ms TTL=109

Ping statistics for 217.147.89.101:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 141ms, Maximum = 142ms, Average = 141ms

C:\Users\Sammy>ping 52.59.121.244

Pinging 52.59.121.244 with 32 bytes of data:
Reply from 52.59.121.244: bytes=32 time=136ms TTL=43
Reply from 52.59.121.244: bytes=32 time=136ms TTL=43
Reply from 52.59.121.244: bytes=32 time=135ms TTL=43
Reply from 52.59.121.244: bytes=32 time=137ms TTL=43

Ping statistics for 52.59.121.244:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 135ms, Maximum = 137ms, Average = 136ms
 
Upvote 0
PING 52.59.121.244 (52.59.121.244): 56 data bytes

64 bytes from 52.59.121.244: icmp_seq=0 ttl=43 time=131.001 ms
64 bytes from 52.59.121.244: icmp_seq=1 ttl=43 time=130.282 ms
64 bytes from 52.59.121.244: icmp_seq=2 ttl=43 time=131.022 ms
64 bytes from 52.59.121.244: icmp_seq=3 ttl=43 time=130.655 ms
64 bytes from 52.59.121.244: icmp_seq=4 ttl=43 time=131.079 ms
64 bytes from 52.59.121.244: icmp_seq=5 ttl=43 time=130.338 ms

--- 52.59.121.244 ping statistics ---

6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 130.282/130.730/131.079/0.327 ms
anita@Anitas-MacBook-Pro ~ % ping 217.147.89.101

PING 217.147.89.101 (217.147.89.101): 56 data bytes
64 bytes from 217.147.89.101: icmp_seq=0 ttl=108 time=129.860 ms
64 bytes from 217.147.89.101: icmp_seq=1 ttl=108 time=129.159 ms
64 bytes from 217.147.89.101: icmp_seq=2 ttl=108 time=129.423 ms
64 bytes from 217.147.89.101: icmp_seq=3 ttl=108 time=129.278 ms
64 bytes from 217.147.89.101: icmp_seq=4 ttl=108 time=129.182 ms

^C
--- 217.147.89.101 ping statistics ---

5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 129.159/129.380/129.860/0.257 ms
 
Upvote 0
Code:
ping 72.5.161.92
PING 72.5.161.92 (72.5.161.92) 56(84) bytes of data.
64 bytes from 72.5.161.92: icmp_seq=1 ttl=41 time=247 ms
64 bytes from 72.5.161.92: icmp_seq=2 ttl=41 time=248 ms
64 bytes from 72.5.161.92: icmp_seq=3 ttl=41 time=247 ms
64 bytes from 72.5.161.92: icmp_seq=4 ttl=41 time=249 ms
64 bytes from 72.5.161.92: icmp_seq=5 ttl=41 time=247 ms
^C
--- 72.5.161.92 ping statistics ---
6 packets transmitted, 5 received, 16.6667% packet loss, time 5007ms
rtt min/avg/max/mdev = 247.038/247.808/248.991/0.766 ms

No gaming.. so dont know.
 
Upvote 0
@sayangr @jelegend @RiCo @Sammy @Yatch Thanks guys. May I get another favour ? May I know the ping on this IP 72.5.161.92 ? And if anyone play apex legends or any other games here how are the pings in Singapore and Europe ? How is the overall experience of jio fiber in gaming ?

Pinging 72.5.161.92 with 32 bytes of data:
Reply from 72.5.161.92: bytes=32 time=54ms TTL=46
Reply from 72.5.161.92: bytes=32 time=54ms TTL=46
Reply from 72.5.161.92: bytes=32 time=55ms TTL=46
Reply from 72.5.161.92: bytes=32 time=53ms TTL=46

Ping statistics for 72.5.161.92:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 55ms, Average = 54ms

Sorry I don't game.
 
Upvote 0
@sayangr @jelegend @RiCo @Sammy @Yatch Thanks guys. May I get another favour ? May I know the ping on this IP 72.5.161.92 ? And if anyone play apex legends or any other games here how are the pings in Singapore and Europe ? How is the overall experience of jio fiber in gaming ?
anita@Anitas-MacBook-Pro ~ % ping 72.5.161.92
PING 72.5.161.92 (72.5.161.92): 56 data bytes
64 bytes from 72.5.161.92: icmp_seq=0 ttl=46 time=56.555 ms
64 bytes from 72.5.161.92: icmp_seq=1 ttl=46 time=56.468 ms
64 bytes from 72.5.161.92: icmp_seq=2 ttl=46 time=56.912 ms
64 bytes from 72.5.161.92: icmp_seq=3 ttl=46 time=57.054 ms
64 bytes from 72.5.161.92: icmp_seq=4 ttl=46 time=56.603 ms
64 bytes from 72.5.161.92: icmp_seq=5 ttl=46 time=56.448 ms
^C


--- 72.5.161.92 ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 56.448/56.673/57.054/0.229 ms

I play Call of duty Vanguard. The ping to EU is approx. 115-125ms, and Singapore 51-54ms. My lowest pings are to Amazon Bahrain servers (37-44ms) The gaming experience is quite good, connection is very stable.

Don't connect to Jio router directly for gaming or internet access. Use another router with good QOS (Like OpenWRT, Netduma R2, Edge router) for connecting to your PC and WiFi internet access. This would cause double NAT issues, but since you would be connecting to dedicated servers for Apex Legends and not Peer to Peer, this should not be a problem. Double NAT does not cause hit registration problems or affect lag.
 
Upvote 0
Back