Announcement

Collapse

Forum Rules

  • No flaming or derogatory remarks, directly or through insinuation.
  • No discussion, sharing or referencing illegal software such as hacks, keygen, cracks and pirated software.
  • No offensive contents, including but not limited to, racism, gore or pornography.
  • No excessive spam/meme, i.e. copious one liners in a short period of time, typing with all caps or posting meme responses (text/image).
  • No trolling, including but not limited to, flame incitation, user provocation or false information distribution.
  • No link spamming or signature advertisements for content not specific to Dota 2.
  • No Dota 2 key requests, sell, trade etc.
  • You may not create multiple accounts for any purpose, including ban evasion, unless expressly permitted by a moderator.

  • Please search before posting. One thread per issue. Do not create another thread if there is an existing one already.
  • Before posting anything, make sure you check out all sticky threads (e.g., this). Do not create new threads about closed ones.
  • It is extremely important that you post in correct forum section.

  • Balance discussion only in Misc.
  • All art related (such as hero model) feedbacks go to Art Feedback Forum.
  • All matchmaking feedback should go here: Matchmaking Feedback
  • All report/low priority issues should go here: Commend/Report/Ban Feedback
  • No specific workshop item feedback. These should go to workshop page of that item.
  • When posting in non-bugs section (such as this), use [Bugs], [Discussion] or [Suggestion] prefix in your thread name.



In case you object some action by a moderator, please contact him directly through PM and explain your concerns politely. If you are still unable to resolve the issue, contact an administrator. Do not drag these issues in public.



All rules are meant to augment common sense, please use them when not conflicted with aforementioned policies.
See more
See less

South East Asia and China Server Information

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Originally posted by FatalTouch View Post
    What does this actually mean and is there any way that i can get it fixed or something like that?
    It seems your ISP network that you use has too much network traffic and this causes inherent delays to your data packets.
    This is synonymous with public roads in rush hour, when too much traffic at peak times causes excessive delays.
    The solution is simple: do not drive in the rush hour unless you have to if you want to avoid those delays.

    Comment


    • 300+ ping

      High ping to SEA servers with high packet loss. Traceroute shows dropped packets.

      Location: Taipei, Taiwan
      ISP: KBRO


      [[email protected] ~]$ traceroute 111.251.233.16
      traceroute to 111.251.233.16 (111.251.233.16), 64 hops max, 52 byte packets
      1 192.168.1.1 (192.168.1.1) 3.369 ms 1.113 ms 0.961 ms
      2 10.33.0.1 (10.33.0.1) 12.376 ms 8.832 ms 7.691 ms
      3 211-76-115-1.static.kbronet.com.tw (211.76.115.1) 9.409 ms 9.996 ms 10.056 ms
      4 211-76-115-254.static.kbronet.com.tw (211.76.115.254) 11.412 ms 11.106 ms 10.726 ms
      5 61-30-166-185.static.tfn.net.tw (61.30.166.185) 11.486 ms
      219-80-114-9.static.tfn.net.tw (219.80.114.9) 9.723 ms
      61-30-166-89.static.tfn.net.tw (61.30.166.89) 9.356 ms
      6 60-199-20-214.static.tfn.net.tw (60.199.20.214) 9.371 ms
      60-199-4-101.static.tfn.net.tw (60.199.4.101) 9.839 ms 9.503 ms
      7 60-199-18-230.static.tfn.net.tw (60.199.18.230) 10.360 ms 8.668 ms 23.911 ms
      8 60-199-17-190.static.tfn.net.tw (60.199.17.190) 10.431 ms 10.691 ms
      60-199-17-166.static.tfn.net.tw (60.199.17.166) 9.956 ms
      9 60-199-17-166.static.tfn.net.tw (60.199.17.166) 10.036 ms
      60-199-17-186.static.tfn.net.tw (60.199.17.186) 9.941 ms
      r4207-s2.hinet.net (210.242.214.158) 12.267 ms
      10 tpdt-3012.hinet.net (220.128.4.178) 14.142 ms 11.898 ms
      r4207-s2.hinet.net (210.242.214.158) 11.996 ms
      11 sczs-3102.hinet.net (220.128.7.117) 13.413 ms 10.901 ms 12.649 ms
      12 sczs-3302.hinet.net (220.128.7.77) 11.395 ms
      sczs-3102.hinet.net (220.128.7.117) 14.428 ms 10.970 ms
      13 h37.s91.ts.hinet.net (168.95.91.37) 13.098 ms 13.093 ms 17.040 ms
      14 * h37.s91.ts.hinet.net (168.95.91.37) 13.507 ms 13.854 ms
      15 * * *
      16 * * *
      17 * * *
      18 * * *
      19 * * *
      20 * * *

      Comment


      • eclubmalaysia

        I have posted my problem of high ping(over 300ms) at #2348

        Plz help me

        Comment


        • Originally posted by 93133795 View Post
          eclubmalaysia
          I have posted my problem of high ping(over 300ms) at #2348
          Plz help me
          Copy

          Comment


          • Originally posted by aguathecat View Post
            High ping to SEA servers with high packet loss. Traceroute shows dropped packets.

            Location: Taipei, Taiwan
            ISP: KBRO
            20 * * *
            We already escalated your case to StarHub backend if they can further optimize the route.
            We will update you the findings.

            Comment


            • What is this IP you are tracing to. This is not one of our servers.

              Originally posted by aguathecat View Post
              High ping to SEA servers with high packet loss. Traceroute shows dropped packets.

              Location: Taipei, Taiwan
              ISP: KBRO


              [[email protected] ~]$ traceroute 111.251.233.16
              traceroute to 111.251.233.16 (111.251.233.16), 64 hops max, 52 byte packets
              1 192.168.1.1 (192.168.1.1) 3.369 ms 1.113 ms 0.961 ms
              2 10.33.0.1 (10.33.0.1) 12.376 ms 8.832 ms 7.691 ms
              3 211-76-115-1.static.kbronet.com.tw (211.76.115.1) 9.409 ms 9.996 ms 10.056 ms
              4 211-76-115-254.static.kbronet.com.tw (211.76.115.254) 11.412 ms 11.106 ms 10.726 ms
              5 61-30-166-185.static.tfn.net.tw (61.30.166.185) 11.486 ms
              219-80-114-9.static.tfn.net.tw (219.80.114.9) 9.723 ms
              61-30-166-89.static.tfn.net.tw (61.30.166.89) 9.356 ms
              6 60-199-20-214.static.tfn.net.tw (60.199.20.214) 9.371 ms
              60-199-4-101.static.tfn.net.tw (60.199.4.101) 9.839 ms 9.503 ms
              7 60-199-18-230.static.tfn.net.tw (60.199.18.230) 10.360 ms 8.668 ms 23.911 ms
              8 60-199-17-190.static.tfn.net.tw (60.199.17.190) 10.431 ms 10.691 ms
              60-199-17-166.static.tfn.net.tw (60.199.17.166) 9.956 ms
              9 60-199-17-166.static.tfn.net.tw (60.199.17.166) 10.036 ms
              60-199-17-186.static.tfn.net.tw (60.199.17.186) 9.941 ms
              r4207-s2.hinet.net (210.242.214.158) 12.267 ms
              10 tpdt-3012.hinet.net (220.128.4.178) 14.142 ms 11.898 ms
              r4207-s2.hinet.net (210.242.214.158) 11.996 ms
              11 sczs-3102.hinet.net (220.128.7.117) 13.413 ms 10.901 ms 12.649 ms
              12 sczs-3302.hinet.net (220.128.7.77) 11.395 ms
              sczs-3102.hinet.net (220.128.7.117) 14.428 ms 10.970 ms
              13 h37.s91.ts.hinet.net (168.95.91.37) 13.098 ms 13.093 ms 17.040 ms
              14 * h37.s91.ts.hinet.net (168.95.91.37) 13.507 ms 13.854 ms
              15 * * *
              16 * * *
              17 * * *
              18 * * *
              19 * * *
              20 * * *

              Comment


              • Now I'm encountering ping problem, it always happen in the afternoon. Either unable to send udp or high ping.
                My IP: 111.251.216.196

                1 1 ms 2 ms 2 ms h254.s98.ts.hinet.net [168.95.98.254]
                2 1 ms 1 ms 1 ms SCZS-3302.hinet.net [168.95.91.38]
                3 1 ms 2 ms 1 ms SCZS-3101.hinet.net [220.128.7.98]
                4 5 ms 5 ms 6 ms TPDT-3011.hinet.net [220.128.1.90]
                5 3 ms 2 ms 4 ms r4103-s2.tp.hinet.net [220.128.3.45]
                6 3 ms 3 ms 2 ms r4003-s2.tp.hinet.net [220.128.3.249]
                7 271 ms 261 ms 258 ms 211-22-33-45.HINET-IP.hinet.net [211.22.33.45]
                8 248 ms 260 ms 258 ms vlan907-an-cat6k-tl2.starhub.net.sg [203.118.3.2
                8]
                9 197 ms 198 ms 199 ms anatll11.starhub.net.sg [203.118.7.34]
                10 208 ms 197 ms 191 ms 203.116.6.238
                11 238 ms 238 ms 241 ms 103-28-54-243.valve.net [103.28.55.243]

                Comment


                • Location : india
                  my ip according to google :59.184.180.210
                  Previously i had pings in the range of 60-120. today it has increased suddenly to 300+
                  my tracert
                  Tracing route to gw.sgp.valve.net [103.28.54.1]
                  over a maximum of 30 hops:

                  1 <1 ms <1 ms <1 ms 192.168.1.1
                  2 63 ms 59 ms 59 ms triband-mum-59.184.191.254.mtnl.net.in [59.184.1
                  91.254]
                  3 60 ms 62 ms 59 ms static-mum-59.185.4.41.mtnl.net.in [59.185.4.41]

                  4 212 ms 208 ms 206 ms AES-Static-177.105.144.59.airtel.in [59.144.105.
                  177]
                  5 235 ms 235 ms 235 ms 61.95.210.117
                  6 341 ms 341 ms 340 ms 203.116.9.161
                  7 351 ms 350 ms 351 ms vlan907-an-cat6k-ts1-r1.starhub.net.sg [203.118.
                  3.215]
                  8 339 ms 338 ms 338 ms anatll11.starhub.net.sg [203.118.7.34]
                  9 340 ms 338 ms 338 ms 203.116.6.238
                  10 343 ms 338 ms 337 ms gw.sgp.valve.net [103.28.54.1]

                  Trace complete.
                  つ ◕_◕ ༽ つ Give Solo Queue Back! Pls

                  Comment


                  • Ive been experiencing alot of spikes on the sea server recently.. my ping or fps never changes but every 10 minutes i get horrible spikes for 2-3 mins...like the hero moves then stops then moves and this happens only on the sea server..

                    My ip : 123.236.254.233

                    My tracert :

                    Microsoft Windows [Version 6.1.7600]
                    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

                    C:\Windows\system32>tracert 103.28.54.1

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

                    1 19 ms 18 ms 20 ms 10.9.243.188
                    2 21 ms 20 ms 21 ms 220.224.150.85
                    3 25 ms 26 ms 25 ms 220.224.150.90
                    4 55 ms 56 ms 60 ms 115.255.252.225
                    5 59 ms 62 ms 59 ms 62.216.147.249
                    6 93 ms 93 ms 96 ms so-7-0-0.0.ejr03.sin001.flagtel.com [62.216.128.
                    73]
                    7 110 ms 113 ms 112 ms 80.77.1.210
                    8 120 ms 120 ms 122 ms vlan907-an-cat6k-tl2.starhub.net.sg [203.118.3.1
                    74]
                    9 124 ms 121 ms 122 ms anatll11.starhub.net.sg [203.118.7.34]
                    10 93 ms 88 ms 89 ms 203.116.6.238
                    11 124 ms 121 ms 121 ms gw.sgp.valve.net [103.28.54.1]

                    Trace complete.

                    plz help!

                    Comment


                    • I'm having high ping since last week. I used to play on sea servers with ~100 ms. Now it has escalated to 500+ ms. My friends are getting less than 150 ms on the sea servers. It seems like I'm the only one affected with this. Help plz.


                      My IP: 197.226.25.212
                      ---Tracert
                      Microsoft Windows [Version 6.2.9200]
                      (c) 2012 Microsoft Corporation. All rights reserved.

                      C:\Users\Appadoo>tracert 103.28.54.1

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

                      1 1 ms 1 ms 1 ms 192.168.1.1
                      2 12 ms 12 ms 12 ms 197.226.0.1
                      3 12 ms 13 ms 13 ms 196.192.102.170
                      4 14 ms 13 ms 13 ms tengig4-1.201-fl.telecomplus.net [196.20.254.173
                      ]
                      5 218 ms 219 ms 218 ms pos10-0.londra7.lon.seabone.net [89.221.43.137]

                      6 554 ms 552 ms 553 ms xe-11-0-0.singapore2.sin.seabone.net [93.186.133
                      .20]
                      7 563 ms 560 ms 561 ms starhub-50.singapore2.sin.seabone.net [93.186.13
                      3.50]
                      8 556 ms 556 ms 555 ms vlan907-an-cat6k-tl2.starhub.net.sg [203.118.3.1
                      74]
                      9 564 ms 564 ms 564 ms anatll11.starhub.net.sg [203.118.7.34]
                      10 564 ms 612 ms 563 ms 203.116.6.238
                      11 563 ms 557 ms 559 ms gw.sgp.valve.net [103.28.54.1]

                      Trace complete.
                      ---

                      Comment


                      • Originally posted by azezezaaa View Post
                        I'm having high ping since last week. I used to play on sea servers with ~100 ms. Now it has escalated to 500+ ms. My friends are getting less than 150 ms on the sea servers. It seems like I'm the only one affected with this. Help plz.


                        My IP: 197.226.25.212
                        ---Tracert
                        Microsoft Windows [Version 6.2.9200]
                        (c) 2012 Microsoft Corporation. All rights reserved.
                        C:\Users\Appadoo>tracert 103.28.54.1
                        Tracing route to gw.sgp.valve.net [103.28.54.1]
                        over a maximum of 30 hops:
                        11 563 ms 557 ms 559 ms gw.sgp.valve.net [103.28.54.1]
                        Trace complete.
                        ---
                        You are from Mauritius, you should choose Valve servers in Europe

                        Comment


                        • Originally posted by Ezpada View Post
                          Ive been experiencing alot of spikes on the sea server recently.. my ping or fps never changes but every 10 minutes i get horrible spikes for 2-3 mins...like the hero moves then stops then moves and this happens only on the sea server..

                          My ip : 123.236.254.233

                          My tracert :
                          Microsoft Windows [Version 6.1.7600]
                          Copyright (c) 2009 Microsoft Corporation. All rights reserved.
                          C:\Windows\system32>tracert 103.28.54.1
                          Tracing route to gw.sgp.valve.net [103.28.54.1]
                          over a maximum of 30 hops:

                          1 19 ms 18 ms 20 ms 10.9.243.188
                          2 21 ms 20 ms 21 ms 220.224.150.85
                          3 25 ms 26 ms 25 ms 220.224.150.90
                          4 55 ms 56 ms 60 ms 115.255.252.225
                          5 59 ms 62 ms 59 ms 62.216.147.249
                          6 93 ms 93 ms 96 ms so-7-0-0.0.ejr03.sin001.flagtel.com [62.216.128.73]
                          7 110 ms 113 ms 112 ms 80.77.1.210
                          8 120 ms 120 ms 122 ms vlan907-an-cat6k-tl2.starhub.net.sg [203.118.3.174]
                          9 124 ms 121 ms 122 ms anatll11.starhub.net.sg [203.118.7.34]
                          10 93 ms 88 ms 89 ms 203.116.6.238
                          11 124 ms 121 ms 121 ms gw.sgp.valve.net [103.28.54.1]
                          Trace complete.
                          plz help!
                          You are from India, usually it is at a bearable 150-225 ping range

                          Comment


                          • Originally posted by Lightee View Post
                            Now I'm encountering ping problem, it always happen in the afternoon. Either unable to send udp or high ping.
                            My IP: 111.251.216.196
                            Can you send us a fresh traceroute (tracert under windows) to
                            103.28.54.1, (Singapore)

                            Comment


                            • ip address:121.54.48.42
                              location: philippines
                              isp: Smart Broadband

                              i got 3 request time out...still i get lag spikes in dota 2
                              C:\Users\Emperio>tracert 103.28.54.1

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

                              1 <1 ms <1 ms 1 ms 192.168.1.1
                              2 * * * Request timed out.
                              3 12 ms 7 ms 12 ms 121.54.48.33
                              4 24 ms 10 ms 17 ms 203.87.160.69
                              5 38 ms 32 ms 57 ms 203.87.132.9
                              6 109 ms 66 ms 40 ms 210.213.244.233.static.pldt.net [210.213.244.233
                              ]
                              7 79 ms 66 ms 50 ms 210.213.132.18.static.pldt.net [210.213.132.18]

                              8 * * * Request timed out.
                              9 * * * Request timed out.
                              10 33 ms 40 ms 34 ms 210.213.128.29.static.pldt.net [210.213.128.29]

                              11 13 ms 26 ms 33 ms 210.213.130.9.static.pldt.net [210.213.130.9]
                              12 61 ms 62 ms 57 ms 210.14.2.186
                              13 108 ms 114 ms 122 ms vlan907-an-cat6k-ts1-r1.starhub.net.sg [203.118.
                              3.215]
                              14 92 ms 100 ms 97 ms anatll11.starhub.net.sg [203.118.7.34]
                              15 117 ms 108 ms 109 ms 203.116.6.238
                              16 119 ms 119 ms 124 ms gw.sgp.valve.net [103.28.54.1]

                              Trace complete.

                              Comment


                              • @Eclub I am noticing that all mtnl users in India are having this 350 ping problem. Since alot of dota2 players in india use mtnl, is it possible for valve to contact MTNL to sort things out?
                                I have tried calling their helpline numbers but the regular call center people are not able to understand the problem, much less solve it. I am hoping maybe Valve has a contact with them and can solve this issue. Thanks.

                                Comment

                                Working...
                                X