DOTA 2 Ping issues? post your solutions and problems here

[Desolator]

Lets keep this thread solely for ping problems and discussions. Also any updates regarding server maintenance and new servers being introduced can also be posted here.


Q: How to check my ping and trace route on a server?
Ever wanted to play on a server from another region but too afraid if you might get high ping and be the lagger in that game? Well now you can check your ping to all of Dota 2 servers before selecting which Server to Find A Match on.

Step 1:Open CMD (Command Prompt) / Network Utility / Terminal


→ Press Windows Key + R on your keyboard to open RUN Window

→ Type in "CMD" and press OK

Step 2:
Pinging the Servers and knowing your Ping

Windows:
Once you have opened up CMD type in "ping SERVER-IP-ADDRESS -t" (without quotes). For trace route type "tracert SERVER-IP-ADDRESS"



Here are the list of IP and Address of Dota 2 Servers:


sgp-1.valve.net - SE Asia 1 (Singapore)
sgp-2.valve.net - SE Asia 2 (Singapore)
syd.valve.net - Australia (Sydney)
sto.valve.net - Russia 1 (Stockholm)
185.25.180.1 - Russia 2 (Stockholm)
vie.valve.net - Europe East (Vienna)
lux.valve.net - Europe West 1(Luxembourg)
146.66.158.1 - Europe West 2 (Luxembourg)
cpt-1.valve.net - South Africa 1 (Cape Town)
197.80.200.1 - South Africa 2 (Cape Town)
196.38.180.1 - South Africa 3 (Johannesburg)
208.78.164.1 - US East (Sterling)
eat.valve.net - US West (Seattle)
gru.valve.net - South America 1 (Sao Paulo)
209.197.29.1 - South America 2 (Sao Paulo)
209.197.25.1 - South America 3 (Sao Paulo)

 

[Farrukhkazimi]

 

[StrikerX]

^
That's more related to server stability than anything else, they can make routing changes on the go.

@StrikerX Ping has gone back down but there are still times I connect to a game and it's giving me 220ish ms, Restarting my router seems to fix this issue sometimes but I need to restart every game its weird. Plus EU routing has gone to shit as well. 300+.

The major problem got resolved but this one I am afraid can't be fixed anytime soon, its a capacity issue, whenever peak load hits load balancing starts hence the high ping (+-70-100ms) @ peak times. Singapore related issues get resolved quickly because there is no real intermediary provider in between, its a direct link somewhat where as in Europe's case there are 2-3 providers involved and they don't exactly cater to these kind of requests.

 

[Sam707]

So, I was just messing around with cmd yesterday. I started pinging 103.28.54.XX prefix. After 103.28.54.5 till .20, all were "request timed out". So did .240 on which I played a game a couple of days ago.

Just thought this info might help.

 

[Legend145]

i don't think this is only happening in dota 2, i cant play most games at peak times due to high ping, letancy and packet loss. Also that that that surfing is getting slower day by day. i think that the issue is in pakistan where bad hardware is used... during peaktime when i tracert ip's some hops that are in pakistan give 70ms instead of 12-20ms during peaktimes. anyways i get 70ms most time and get 220ms + during 7pm-2am.

i can help with one thing that could not reduce ping but can reduce input delay which can help.

1) go to game properties of Dota 2 on Steam and click on "Set Launch Options" and put "-console"
2) Start Dota 2 which will open with a console where you would type commands... just type there "net_graph 1"
3) that will open a stats graph which would show some values... just move the console a side and focus on the Value "lerp" by default it would be "66.7 ms"
4) put these commands into the console.. "cl_interp 0" and "cl_interp_ratio 1" this will reduce the input lag nothing else.
5) now focus on the lerp value again it should be "33.3 ms" this means u have removed input delay by 33.4 ms which can help bypass some of the delay

if you want to remove this than just put "-autoconfig" in the launch options and start dota 2 but u would need to change ur settings again... after that close dota 2 and remove the "-autoconfig" from the launch options.
hope this helps

[EDIT] Just to tell by applying these settings u will have to compromise smoothing so ull see some wrong predictions the game will make but it wont affect your gameplay....

 

[Sam707]

More effed pings now (I didnt try the above thing, just saying) sgp-1.valve.net gives the standard 130 ms I usually got when playing. In game, It was 350ms and last night it was 500 ms. This is getting out of hand. PTCL helpline is of no help in this regard...

 

[dasheikh]

evening times pings will be effed no matter who you call and no matter what you do until they fix the local bottle neck.

route to 146.66.152.1 has been switched back to via france -

C:\Users\idossul>tracert 146.66.152.1


Tracing route to gw.lux.valve.net [146.66.152.1]
over a maximum of 30 hops:


1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 9 ms 9 ms 39.50.128.1
3 9 ms 8 ms 8 ms 10.0.4.241
4 10 ms 9 ms 9 ms 10.0.1.13
5 9 ms 8 ms 9 ms 203.99.170.145
6 12 ms 11 ms 11 ms rwp44.pie.net.pk [221.120.251.177]
7 10 ms 11 ms 11 ms static.khi77.pie.net.pk [202.125.128.171]
8 120 ms 118 ms 124 ms 213.242.115.37
9 119 ms 118 ms 120 ms ae-5-6.bar2.Marseille1.Level3.net [4.69.151.13]


10 138 ms 138 ms 138 ms ae-15-15.ebr4.Frankfurt1.Level3.net [4.69.143.24
6]
11 138 ms 138 ms 137 ms ae-64-64.csw1.Frankfurt1.Level3.net [4.69.163.18
]
12 137 ms 137 ms 138 ms ae-62-62.ebr2.Frankfurt1.Level3.net [4.69.140.17
]
13 137 ms 159 ms 137 ms ae-19-19.car1.Luxembourg1.Level3.net [4.69.148.2
29]
14 146 ms 144 ms 144 ms gw.lux.valve.net [146.66.152.1]


Trace complete.

 

[Sigurat]

evening times pings will be effed no matter who you call and no matter what you do until they fix the local bottle neck.

route to 146.66.152.1 has been switched back to via france -

C:\Users\idossul>tracert 146.66.152.1


Tracing route to gw.lux.valve.net [146.66.152.1]
over a maximum of 30 hops:


1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 9 ms 9 ms 39.50.128.1
3 9 ms 8 ms 8 ms 10.0.4.241
4 10 ms 9 ms 9 ms 10.0.1.13
5 9 ms 8 ms 9 ms 203.99.170.145
6 12 ms 11 ms 11 ms rwp44.pie.net.pk [221.120.251.177]
7 10 ms 11 ms 11 ms static.khi77.pie.net.pk [202.125.128.171]
8 120 ms 118 ms 124 ms 213.242.115.37
9 119 ms 118 ms 120 ms ae-5-6.bar2.Marseille1.Level3.net [4.69.151.13]


10 138 ms 138 ms 138 ms ae-15-15.ebr4.Frankfurt1.Level3.net [4.69.143.24
6]
11 138 ms 138 ms 137 ms ae-64-64.csw1.Frankfurt1.Level3.net [4.69.163.18
]
12 137 ms 137 ms 138 ms ae-62-62.ebr2.Frankfurt1.Level3.net [4.69.140.17
]
13 137 ms 159 ms 137 ms ae-19-19.car1.Luxembourg1.Level3.net [4.69.148.2
29]
14 146 ms 144 ms 144 ms gw.lux.valve.net [146.66.152.1]


Trace complete.

Yeah the routing for luxembourg has been reverted to what it was before so now EU West pings are low again like they used to be. They've also fixed routing to sgp-1 which is 103.28.54.1. In return for this they've messed up routing to sgp-2 103.10.24.1 and a multitude of sub clusters on which SEA games are hosted. 80% of the time you're bound to get 180-400 ms on SEA while rarely getting the 130. I have tried to contact ptcl without success. I've contacted e-club Malaysia the company that hosts the SEA servers and while they had some maintenance issues last month they have since fixed everything from their end so now I think it's just our ISP that is causing the problems :/

 

[shoby80]

I am getting below from EU-West... can anyone confirm whether the route is restored or not. I think its still at 250ms

C:\Users\Shoaib>tracert 146.66.152.1


Tracing route to gw.lux.valve.net [146.66.152.1]
over a maximum of 30 hops:


1 1 ms 1 ms 2 ms 172.24.41.1
2 27 ms 44 ms 36 ms 203.99.169.18
3 38 ms 28 ms 25 ms 10.0.4.1
4 47 ms 26 ms 26 ms 203.99.170.145
5 37 ms 67 ms 43 ms 221.120.251.177
6 59 ms 38 ms 39 ms static.khi77.pie.net.pk [202.125.128.170]
7 * * * Request timed out.
8 186 ms 214 ms 261 ms be2346.mag21.mrs01.atlas.cogentco.com [154.54.38
.174]
9 138 ms 143 ms 174 ms be2346.ccr22.mrs01.atlas.cogentco.com [154.54.38
.173]
10 195 ms * 200 ms te7-4.ccr01.mil01.atlas.cogentco.com [130.117.3.
102]
11 274 ms 303 ms 258 ms 130.117.14.198
12 276 ms 250 ms 282 ms xe-9-2-1.fra61.ip4.tinet.net [89.149.183.141]
13 249 ms 251 ms 267 ms gw.lux.valve.net [146.66.152.1]


Trace complete.

 

[shoby80]

There is a strange problem going on with PTCL , me and my friend are both from Karachi and we both use PTCL 4 mb DSL, however he lives in Gulistan E Jauhar whereas i Live in Gulshan-e-Iqbal. (merely 5 km away from each other and have different ptcl exchanges). Now the issue is his Ping to EU West is 133ms and Mine is 240ms. Whereas is my SEA ping is 133 and his ping is 250ms. Is PTCL routing from different lines? or its something else. Also please share me the email + number etc where i can complain about this.

 

[w00t]

450 ping on SEA and 350 on EU west. :/

 

[StrikerX]

There is a strange problem going on with PTCL , me and my friend are both from Karachi and we both use PTCL 4 mb DSL, however he lives in Gulistan E Jauhar whereas i Live in Gulshan-e-Iqbal. (merely 5 km away from each other and have different ptcl exchanges). Now the issue is his Ping to EU West is 133ms and Mine is 240ms. Whereas is my SEA ping is 133 and his ping is 250ms. Is PTCL routing from different lines? or its something else. Also please share me the email + number etc where i can complain about this.

Post tracerts, its not like different routing for different lines, its rather different routing for different gateways depending on the regional IP prefixes assigned.

Khair, post tracerts, SEA ping should be <200ms for everyone @ non-peak times.

450 ping on SEA and 350 on EU west. :/

Tracert post kia karo panday, ping shing nai

 

[Sam707]

Tracing route to sgp-1.valve.net [103.28.54.1]
over a maximum of 30 hops:


1 <1 ms <1 ms <1 ms MyRouter.Home [192.168.1.1]
2 * 54 ms * 39.32.0.1
3 * * * Request timed out.
4 40 ms 78 ms 40 ms 10.0.1.2
5 63 ms 63 ms 63 ms 203.99.170.250
6 74 ms 69 ms 67 ms rwp44.pie.net.pk [221.120.253.25]
7 65 ms 66 ms 65 ms rwp44.pie.net.pk [221.120.254.30]
8 64 ms 63 ms 63 ms static-khi-ni02-swa.pie.net.pk [202.125.128.180]


9 140 ms 139 ms 140 ms habib-rafiq.khi77d2.pie.net.pk [202.125.129.218]


10 209 ms 205 ms 197 ms sgp-1.valve.net [103.28.54.1]


Trace complete.

HELP ME!!!!

 

[StrikerX]

Tracing route to sgp-1.valve.net [103.28.54.1]
over a maximum of 30 hops:


1 <1 ms <1 ms <1 ms MyRouter.Home [192.168.1.1]
2 * 54 ms * 39.32.0.1
3 * * * Request timed out.
4 40 ms 78 ms 40 ms 10.0.1.2
5 63 ms 63 ms 63 ms 203.99.170.250
6 74 ms 69 ms 67 ms rwp44.pie.net.pk [221.120.253.25]
7 65 ms 66 ms 65 ms rwp44.pie.net.pk [221.120.254.30]
8 64 ms 63 ms 63 ms static-khi-ni02-swa.pie.net.pk [202.125.128.180]


9 140 ms 139 ms 140 ms habib-rafiq.khi77d2.pie.net.pk [202.125.129.218]


10 209 ms 205 ms 197 ms sgp-1.valve.net [103.28.54.1]


Trace complete.

HELP ME!!!!

That's the best you'll get at peak-time for now.

 

[Desolator]

Added server IPs and guide on how to check for pings and tracert on a particular server

 

[XStrikerExtreme]

There is a strange problem going on with PTCL , me and my friend are both from Karachi and we both use PTCL 4 mb DSL, however he lives in Gulistan E Jauhar whereas i Live in Gulshan-e-Iqbal. (merely 5 km away from each other and have different ptcl exchanges). Now the issue is his Ping to EU West is 133ms and Mine is 240ms. Whereas is my SEA ping is 133 and his ping is 250ms. Is PTCL routing from different lines? or its something else. Also please share me the email + number etc where i can complain about this.

run tracert for both servers from different areas as you said. It will reveal what route ptcl is using for both. If irs same route then something else is wrong.

 

[StrikerX]

dev.dota2.com/showthread.php?t=72226&page=40&p=1032124#post1032124


its happening !

Super high ping. Posted tracert there. Let's see.

One of my friends (Lahore) was getting sub-100 pings though. His ISP isn't some well-known one.

Forwarded :laugh1: currently its going via EU which it normally does for all waisay...

p.s they know, expect changes 'soon'.

 

[Desolator]

Super high ping. Posted tracert there. Let's see.

One of my friends (Lahore) was getting sub-100 pings though. His ISP isn't some well-known one.

They are still configuring it as it is mentioned in the post as well that optimization is still under way. In any case, you should post your tracert in the dev thread so they can take action in advance.

 

[StrikerX]

Ok, don't expect changes soon, PTCL at the moment can't peer directly. They might make some changes but currently, they can't peer directly. :laugh1:

Spoiler: show

That's what has been conveyed to me.

Spoiler: show

Basically, bandwidth limitation towards there. They will change some things around IF they think its feasible.

 

[dasheikh]

Ok, don't expect changes soon, PTCL at the moment can't peer directly. They might make some changes but currently, they can't peer directly. :laugh1:

Spoiler: show

That's what has been conveyed to me.

Spoiler: show

Basically, bandwidth limitation towards there. They will change some things around IF they think its feasible.

Yep, got a reply from the ptclcares gent; said they were aware but cannot peer directly due to "certain limitations" and that they were working on it.

Maybe transworld would be better in that regard?