Can anyone do a ping test for me in cmd for valorant mumbai servers

  • Thread starter Thread starter kanansrin
  • Start date Start date
  • Replies Replies 66
  • Views Views 37,742
Messages
165
Location
Ranaghat
ISP
Jio Fiber
Please if some of you can share a ping test in cmd and also if possible in game ping of mumbai servers will be helpful


Ip s for cmd
1) 75.2.66.166
2) 99.83.136.104

Thanks in advance
 


not on jio myself but i hope this helps. all these probes are on Jio
 
Code:
root@OpenWrt:~# ping 75.2.66.166
PING 75.2.66.166 (75.2.66.166): 56 data bytes
64 bytes from 75.2.66.166: seq=0 ttl=118 time=17.092 ms
64 bytes from 75.2.66.166: seq=1 ttl=118 time=17.563 ms
64 bytes from 75.2.66.166: seq=2 ttl=118 time=16.887 ms
64 bytes from 75.2.66.166: seq=3 ttl=118 time=17.435 ms
^C
--- 75.2.66.166 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 16.887/17.244/17.563 ms
root@OpenWrt:~# ping 99.83.136.104
PING 99.83.136.104 (99.83.136.104): 56 data bytes
64 bytes from 99.83.136.104: seq=0 ttl=118 time=17.217 ms
64 bytes from 99.83.136.104: seq=1 ttl=118 time=17.117 ms
64 bytes from 99.83.136.104: seq=2 ttl=118 time=17.465 ms
64 bytes from 99.83.136.104: seq=3 ttl=118 time=16.958 ms
^C
--- 99.83.136.104 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 16.958/17.189/17.465 ms
 
Something which you should know is that Valorant's Mumbai servers are hosted on AWS. My ISP is present along with Amazon in EIX Kolkata, which has 6-8ms ping from my location. Due to this, both the valorant IPs too have similar ping, but the ping in-game is similar to those for other Mumbai servers(35-50ms). So IMO the traceroute wouldn't suggest much.
 
@WandereR Bt i live in ranaghat my in game ping to valorant servers is 85 to 110....thats why i was asking that means its a problem of jio fiber in my area
 


i live in ranaghat my in game ping to valorant servers is 85 to 110
JioFiber has poor pings even in Jharkhand. Talk to cc if they have one. If they understand your problem, I'm sure they can bring it down to 50-60ms if not lesser.
 
@wandererfrom 7 days they are resolving my issue bt still there is no update.....very bad jio fiber routing is very bad
 
Code:
Users-PC:~ raj$ ping 75.2.66.166
PING 75.2.66.166 (75.2.66.166): 56 data bytes
64 bytes from 75.2.66.166: icmp_seq=0 ttl=118 time=34.797 ms
64 bytes from 75.2.66.166: icmp_seq=1 ttl=118 time=15.047 ms
64 bytes from 75.2.66.166: icmp_seq=2 ttl=118 time=15.258 ms
64 bytes from 75.2.66.166: icmp_seq=3 ttl=118 time=15.636 ms
64 bytes from 75.2.66.166: icmp_seq=4 ttl=118 time=15.646 ms
^C
--- 75.2.66.166 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 15.047/19.277/34.797/7.763 ms
Users-PC:~ raj$ ping 99.83.136.104
PING 99.83.136.104 (99.83.136.104): 56 data bytes
64 bytes from 99.83.136.104: icmp_seq=0 ttl=120 time=17.007 ms
64 bytes from 99.83.136.104: icmp_seq=1 ttl=120 time=14.881 ms
64 bytes from 99.83.136.104: icmp_seq=2 ttl=120 time=17.902 ms
64 bytes from 99.83.136.104: icmp_seq=3 ttl=120 time=17.448 ms
64 bytes from 99.83.136.104: icmp_seq=4 ttl=120 time=15.174 ms
64 bytes from 99.83.136.104: icmp_seq=5 ttl=120 time=16.507 ms
64 bytes from 99.83.136.104: icmp_seq=6 ttl=120 time=12.027 ms
64 bytes from 99.83.136.104: icmp_seq=7 ttl=120 time=12.581 ms
64 bytes from 99.83.136.104: icmp_seq=8 ttl=120 time=15.518 ms
64 bytes from 99.83.136.104: icmp_seq=9 ttl=120 time=13.727 ms
64 bytes from 99.83.136.104: icmp_seq=10 ttl=120 time=13.543 ms
64 bytes from 99.83.136.104: icmp_seq=11 ttl=120 time=13.938 ms
^C
--- 99.83.136.104 ping statistics ---
13 packets transmitted, 12 packets received, 7.7% packet loss
round-trip min/avg/max/stddev = 12.027/15.021/17.902/1.839 ms
 

Back