High Latency and DCs
Re: High Latency and DCs
You have a timeout in 8th hop, that might cause the lag. Try doing a pathping to the server it will show you if packets get lost along the way. Assuming you have Windows, just replace tracert with pathping in the command line...
Re: High Latency and DCs
Tracing route to login.truewow.org [184.154.79.250]
over a maximum of 30 hops:
0 STLK3R-PC [115.98.161.77]
1 10.145.0.1
2 202.88.174.1
3 202.88.174.66
4 202.88.174.61
5 125.16.0.189
6 203.101.100.105
7 115.248.226.22
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 STLK3R-PC [115.98.161.77]
0/ 100 = 0% |
1 11ms 0/ 100 = 0% 0/ 100 = 0% 10.145.0.1
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% 202.88.174.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% 202.88.174.66
0/ 100 = 0% |
4 12ms 0/ 100 = 0% 0/ 100 = 0% 202.88.174.61
0/ 100 = 0% |
5 30ms 0/ 100 = 0% 0/ 100 = 0% 125.16.0.189
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 203.101.100.105
0/ 100 = 0% |
7 81ms 0/ 100 = 0% 0/ 100 = 0% 115.248.226.22
Trace complete.
Thank you for looking into this , here is the pathping which was taken during non peak hours.
over a maximum of 30 hops:
0 STLK3R-PC [115.98.161.77]
1 10.145.0.1
2 202.88.174.1
3 202.88.174.66
4 202.88.174.61
5 125.16.0.189
6 203.101.100.105
7 115.248.226.22
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 STLK3R-PC [115.98.161.77]
0/ 100 = 0% |
1 11ms 0/ 100 = 0% 0/ 100 = 0% 10.145.0.1
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% 202.88.174.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% 202.88.174.66
0/ 100 = 0% |
4 12ms 0/ 100 = 0% 0/ 100 = 0% 202.88.174.61
0/ 100 = 0% |
5 30ms 0/ 100 = 0% 0/ 100 = 0% 125.16.0.189
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 203.101.100.105
0/ 100 = 0% |
7 81ms 0/ 100 = 0% 0/ 100 = 0% 115.248.226.22
Trace complete.
Thank you for looking into this , here is the pathping which was taken during non peak hours.
Re: High Latency and DCs
100% packet loss at one exchange point might explain the lag. Most probably the company providing this exchange point has some problems and they will have to fix it on their end, which should not take long. Try tracerouting and pathpinging our server in different times to see if anything changes. If the issue persist, and you will see * in the traceroute and high percentage of lost packets in the pathping, you may try contacting your ISP to see if they can find out more about the problem.Brizo wrote: 6 --- 100/ 100 =100% 100/ 100 =100% 203.101.100.105
Re: High Latency and DCs
Thank you for the help tia , i am gone change my ISP . if do need to ask what shd i show em .. shd i show them this pathping ?
Re: High Latency and DCs
I would not contact / change ISP straight away if there is a time-out on some hand over point. I would do that if the lag persists, and the traceroutes and pathpings show the same hop is involved.
You could do more traceroutes and pathpings in different times and different zones when playing (like in city, questing, raiding etc) to have more reports to look into first and contact ISP only if the lag persists for a longer period.
You could do more traceroutes and pathpings in different times and different zones when playing (like in city, questing, raiding etc) to have more reports to look into first and contact ISP only if the lag persists for a longer period.
Who is online
Users browsing this forum: No registered users and 6 guests