High ping in game while low ping in cmd

  • Thread starter Thread starter BugMeOut
  • Start date Start date
  • Replies Replies 9
  • Views Views 3,701
Messages
48
Location
India
ISP
Jio GigaFiber
I am a getting high ping (300ms+) in valorant occasionally with a 70ms nearly constant in valorant. Ping test in cmd gies average 22ms with zero packet loss. I am using cloudfare dns(1.1.1.1-1.0.0.1) Is there anything I an do to improve it. I live in udaipur rajasthan and play on mumbai servers
 
The IPs are global accelerators whereas the ping which the game shows is the actual ping to the server.
I guess 5-7ms on the above IPs and 25-35ms In-game for Mumbai servers.
Not much that can be done from your end, can try a VPN if that improves it.
 
Code:
C:\WINDOWS\system32>ping 3.6.0.0


Pinging 3.6.0.0 with 32 bytes of data:
Reply from 3.6.0.0: bytes=32 time=37ms TTL=239
Reply from 3.6.0.0: bytes=32 time=36ms TTL=239
Reply from 3.6.0.0: bytes=32 time=37ms TTL=239
Reply from 3.6.0.0: bytes=32 time=37ms TTL=239


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

Code:
C:\WINDOWS\system32>tracert 3.6.0.0

Tracing route to ec2-3-6-0-0.ap-south-1.compute.amazonaws.com [3.6.0.0]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  reliance.reliance [192.168.29.1]
  2     2 ms     2 ms     1 ms  10.27.0.1
  3     8 ms     8 ms     7 ms  172.27.7.87
  4     8 ms     8 ms     8 ms  172.16.3.155
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    65 ms    65 ms    66 ms  52.46.167.238
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14    42 ms    41 ms    41 ms  52.95.66.144
 15    50 ms    42 ms    40 ms  52.95.64.184
 16    40 ms    42 ms    40 ms  52.95.64.181
 17    37 ms    37 ms    38 ms  52.95.66.107
 18    36 ms    35 ms    35 ms  52.95.65.137
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24    35 ms    35 ms    35 ms  ec2-3-6-0-0.ap-south-1.compute.amazonaws.com [3.6.0.0]

Trace complete.
half than in-game ping
 
Last edited:
You should probably mail Jio care to get the routing fixed.
 
There's always around 5-10ms extra ping when in the game for me.

Pinging 3.6.0.0 with 32 bytes of data:
Reply from 3.6.0.0: bytes=32 time=33ms TTL=236
Reply from 3.6.0.0: bytes=32 time=33ms TTL=236
Reply from 3.6.0.0: bytes=32 time=33ms TTL=236
Reply from 3.6.0.0: bytes=32 time=36ms TTL=236
Tracing route to ec2-3-6-0-0.ap-south-1.compute.amazonaws.com [3.6.0.0]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms reliance.reliance [192.168.29.1]
2 2 ms 1 ms 1 ms 10.28.144.1
3 12 ms 11 ms 11 ms 172.31.1.206
4 11 ms 11 ms 11 ms 192.168.61.68
5 12 ms 11 ms 11 ms 172.26.77.101
6 12 ms 12 ms 12 ms 172.26.75.99
7 11 ms 11 ms 11 ms 192.168.61.16
8 13 ms 12 ms 13 ms 192.168.61.17
9 14 ms 13 ms 14 ms 172.31.2.39
10 15 ms 14 ms 14 ms 99.83.67.66
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 49 ms 36 ms 36 ms 52.95.66.74
17 40 ms 40 ms 40 ms 52.95.64.178
18 34 ms 34 ms 34 ms 52.95.64.177
19 33 ms 34 ms 38 ms 52.95.66.63
20 34 ms 33 ms 37 ms 52.95.67.192
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 33 ms 33 ms 33 ms ec2-3-6-0-0.ap-south-1.compute.amazonaws.com [3.6.0.0]

S0L7pj1.png
 
Back