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

kanansrin · Jan 10, 2021

@Rajneesh Rana thanks for helping and also evey one for sharing ....in which i can see that the problem is in my area only

WandereR · Jan 10, 2021

Instead of posting just the ping, it would be better to share the traceroute.

Netmagic · Jan 10, 2021

Pinging 75.2.66.166 with 32 bytes of data:
Reply from 75.2.66.166: bytes=32 time=2ms TTL=121
Reply from 75.2.66.166: bytes=32 time=3ms TTL=121
Reply from 75.2.66.166: bytes=32 time=6ms TTL=121
Reply from 75.2.66.166: bytes=32 time=1ms TTL=121

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

@kanansrin look this is GTPL KCBPL broadband, how they hijacked ICMP.

Gaurav15 · Jan 10, 2021

PING 75.2.66.166 (75.2.66.166): 56 data bytes
64 bytes from 75.2.66.166: seq=0 ttl=119 time=10.653 ms
64 bytes from 75.2.66.166: seq=1 ttl=119 time=10.719 ms
64 bytes from 75.2.66.166: seq=2 ttl=119 time=11.553 ms
64 bytes from 75.2.66.166: seq=3 ttl=119 time=10.779 ms
64 bytes from 75.2.66.166: seq=4 ttl=119 time=10.650 ms

--- 75.2.66.166 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 10.650/10.870/11.553 ms

PING 99.83.136.104 (99.83.136.104): 56 data bytes
64 bytes from 99.83.136.104: seq=0 ttl=119 time=14.759 ms
64 bytes from 99.83.136.104: seq=1 ttl=119 time=15.653 ms
64 bytes from 99.83.136.104: seq=2 ttl=119 time=14.794 ms
64 bytes from 99.83.136.104: seq=3 ttl=119 time=14.958 ms
64 bytes from 99.83.136.104: seq=4 ttl=119 time=14.812 ms

--- 99.83.136.104 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 14.759/14.995/15.653 ms

WandereR · Jan 17, 2021

The ping here is around 60ms and ingame it's 140ms. couldn't expect any worse.

alfaz_rayin · Jan 17, 2021

Code:

PS C:\Windows\system32> ping 75.2.66.166

Pinging 75.2.66.166 with 32 bytes of data:
Reply from 75.2.66.166: bytes=32 time=3ms TTL=119
Reply from 75.2.66.166: bytes=32 time=3ms TTL=119
Reply from 75.2.66.166: bytes=32 time=3ms TTL=119
Reply from 75.2.66.166: bytes=32 time=3ms TTL=119

Ping statistics for 75.2.66.166:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 3ms, Average = 3ms
PS C:\Windows\system32> ping 99.83.136.104

Pinging 99.83.136.104 with 32 bytes of data:
Reply from 99.83.136.104: bytes=32 time=3ms TTL=119
Reply from 99.83.136.104: bytes=32 time=3ms TTL=119
Reply from 99.83.136.104: bytes=32 time=3ms TTL=119
Reply from 99.83.136.104: bytes=32 time=3ms TTL=119

Ping statistics for 99.83.136.104:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 3ms, Average = 3ms
PS C:\Windows\system32>

MTNL Mumbai. So Jio routing is sucky as usual.

Code:

PS C:\Windows\system32> tracert 75.2.66.166

Tracing route to a2c926c3ec71a09d3.awsglobalaccelerator.com [75.2.66.166]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  RT-AX88U-8970 [192.168.1.1]
  2     2 ms     2 ms     2 ms  static-mum-182.56.0.1.mtnl.net.in [182.56.0.1]
  3     4 ms     3 ms     3 ms  static-mum-59.185.210.193.mtnl.net.in [59.185.210.193]
  4     3 ms     2 ms     3 ms  static-mum-59.185.210.194.mtnl.net.in [59.185.210.194]
  5     3 ms     5 ms     2 ms  115.114.89.61.static-Mumbai.vsnl.net.in [115.114.89.61]
  6     3 ms     3 ms     3 ms  172.23.78.233
  7     3 ms     2 ms     3 ms  172.23.78.238
  8     3 ms     3 ms     3 ms  115.110.234.234.static.Mumbai.vsnl.net.in [115.110.234.234]
  9     5 ms     9 ms     5 ms  52.95.66.134
 10     4 ms     3 ms     3 ms  52.95.66.141
 11     4 ms     7 ms     3 ms  52.95.67.225
 12     4 ms     3 ms     3 ms  52.95.67.118
 13     3 ms     3 ms     3 ms  a2c926c3ec71a09d3.awsglobalaccelerator.com [75.2.66.166]

Trace complete.
PS C:\Windows\system32>

kanansrin · Jan 26, 2021

A great update and a kind of success i have done...after getting the high ping to mumbai server in valorant and fedup of complaining to cc of jio ...i complained in the pg portal and to a great news the whole town where i live got the ping fixed and now the ping is 30ms which was early 70ms-100ms .this is the ingame ping

WandereR · Jan 26, 2021

That's a good news. I have complained about high ping in general, if they don't do anything I will try the pgportal thing.

royalroy · Jan 27, 2021

Hi, @kanansrin. How is Jiofiber installed in Ranaghat (I presume this is Nadia's Ranaghat)? How did you contact them for installation? Is it widespread yet in Ranaghat? Jiofiber is yet to arrive in Bolpur. So, I am asking these

upal · Jan 27, 2021

Pinging 75.2.66.166 with 32 bytes of data:
Reply from 75.2.66.166: bytes=32 time=2ms TTL=120
Reply from 75.2.66.166: bytes=32 time=2ms TTL=120
Reply from 75.2.66.166: bytes=32 time=3ms TTL=120
Reply from 75.2.66.166: bytes=32 time=3ms TTL=120

Pinging 75.2.66.166 with 32 bytes of data:
Reply from 75.2.66.166: bytes=32 time=3ms TTL=120
Reply from 75.2.66.166: bytes=32 time=3ms TTL=120
Reply from 75.2.66.166: bytes=32 time=2ms TTL=120
Reply from 75.2.66.166: bytes=32 time=3ms TTL=120

Pretty decent