Page 153 of 991 FirstFirst ... 53 103 143 151 152 153 154 155 163 203 253 653 ... LastLast
Results 1,521 to 1,530 of 9906

Thread: South East Asia and China Server Information

  1. #1521
    Basic Member
    Join Date
    Nov 2012
    Posts
    30
    sometimes it lags and it will stuck i douno why.. today i played 2 games no lag but ping goes high and it will cm to normal..so pls fix this problem..

  2. #1522
    Basic Member
    Join Date
    Nov 2012
    Posts
    30
    I traced everything..Before i was getting 85 to 90 now 160+ i douno why. so pls see this problem and solve...

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

    C:\Users\VikramHolla>tracert 124.125.45.118

    Tracing route to VikramHolla-PC [124.125.45.118]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms VikramHolla-PC [124.125.45.118]

    Trace complete.

    C:\Users\VikramHolla>tracert 203.116.1.50

    Tracing route to dsts1.starhub.net.sg [203.116.1.50]
    over a maximum of 30 hops:

    1 232 ms 252 ms 134 ms 10.9.240.80
    2 29 ms 28 ms 28 ms 220.224.183.137
    3 40 ms 38 ms 28 ms 220.224.183.142
    4 56 ms 56 ms 58 ms 115.255.252.57
    5 123 ms 78 ms 93 ms 62.216.147.73
    6 133 ms 159 ms 131 ms so-1-0-0.0.pjr01.hkg005.flagtel.com [85.95.25.23
    7]
    7 133 ms 134 ms 145 ms so-5-0-0.0.cjr03.hkg003.flagtel.com [85.95.25.21
    8]
    8 130 ms 157 ms 131 ms xe-0-2-0.0.cji01.hkg003.flagtel.com [62.216.128.
    30]
    9 165 ms 173 ms 166 ms 119.27.63.54
    10 161 ms 160 ms 161 ms vlan907-an-cat6k-tl1.starhub.net.sg [203.118.3.2
    37]
    11 163 ms 162 ms 167 ms dsts2.starhub.net.sg [203.118.7.20]
    12 161 ms 173 ms 160 ms dsts1.starhub.net.sg [203.116.1.50]

    Trace complete.

    C:\Users\VikramHolla>tracert 203.118.5.4

    Tracing route to vlan911-an-cat6k-ts-2-rsm1.starhub.net.sg [203.118.5.4]
    over a maximum of 30 hops:

    1 22 ms 21 ms 22 ms 10.9.240.80
    2 35 ms 29 ms 29 ms 220.224.183.137
    3 29 ms 29 ms 28 ms 220.224.183.142
    4 62 ms 68 ms 62 ms 115.255.252.57
    5 61 ms 54 ms 61 ms 62.216.147.73
    6 133 ms 164 ms 132 ms 85.95.26.237
    7 152 ms 140 ms 133 ms so-5-0-0.0.cjr03.hkg003.flagtel.com [85.95.25.21
    8]
    8 132 ms 131 ms 141 ms xe-0-2-0.0.cji01.hkg003.flagtel.com [62.216.128.
    30]
    9 167 ms 165 ms 168 ms 119.27.63.54
    10 168 ms 165 ms 166 ms vlan907-an-cat6k-tl2.starhub.net.sg [203.118.3.2
    38]
    11 273 ms 165 ms 164 ms vlan911-an-cat6k-ts-2-rsm1.starhub.net.sg [203.1
    18.5.4]

    Trace complete.

    C:\Users\VikramHolla>tracert 203.118.3.228

    Tracing route to anutli10.starhub.net.sg [203.118.3.228]
    over a maximum of 30 hops:

    1 22 ms 23 ms 21 ms 10.9.240.80
    2 35 ms 27 ms 31 ms 220.224.183.137
    3 29 ms 30 ms 28 ms 220.224.183.142
    4 57 ms 92 ms 74 ms 115.255.252.57
    5 376 ms 486 ms 341 ms 62.216.147.73
    6 172 ms 189 ms 301 ms 85.95.26.237
    7 203 ms 169 ms 133 ms so-5-0-0.0.cjr03.hkg003.flagtel.com [85.95.25.21
    8]
    8 154 ms 167 ms 179 ms xe-0-2-0.0.cji01.hkg003.flagtel.com [62.216.128.
    30]
    9 242 ms 260 ms 296 ms 119.27.63.54
    10 anutli10.starhub.net.sg [203.118.3.228] reports: Destination net unreachab
    le.

    Trace complete.

    C:\Users\VikramHolla>tracert 63.218.211.117

    Tracing route to ten3-7.br01.hkg15.pccwbtn.net [63.218.211.117]
    over a maximum of 30 hops:

    1 39 ms 42 ms 30 ms 10.9.240.80
    2 29 ms 42 ms 42 ms 220.224.183.137
    3 29 ms 27 ms 27 ms 220.224.183.142
    4 57 ms 55 ms 76 ms 115.255.252.57
    5 241 ms 239 ms 352 ms 62.216.147.101
    6 141 ms 129 ms * so-1-3-0.0.pjr02.hkg005.flagtel.com [85.95.25.11
    8]
    7 355 ms 350 ms 321 ms so-5-0-0.0.cjr04.hkg003.flagtel.com [85.95.25.21
    4]
    8 283 ms 243 ms 251 ms btn3-10G.hkix.net [202.40.161.89]
    9 265 ms 406 ms 532 ms ten3-7.br01.hkg15.pccwbtn.net [63.218.211.117]

    Trace complete.

    C:\Users\VikramHolla>tracert 62.216.137.21

    Tracing route to so-0-0-0.0.cjr03.hkg003.flagtel.com [62.216.137.21]
    over a maximum of 30 hops:

    1 34 ms 23 ms 88 ms 10.9.240.80
    2 28 ms 27 ms 28 ms 220.224.183.137
    3 27 ms 27 ms 28 ms 220.224.183.142
    4 57 ms 61 ms 61 ms 115.255.252.57
    5 89 ms 73 ms 85 ms 62.216.147.73
    6 129 ms 129 ms 129 ms so-1-0-0.0.pjr01.hkg005.flagtel.com [85.95.25.23
    7]
    7 133 ms 133 ms 141 ms so-0-0-0.0.cjr03.hkg003.flagtel.com [62.216.137.
    21]

    Trace complete.

    C:\Users\VikramHolla>tracert 85.95.25.117

    Tracing route to so-3-0-0.0.pjr02.mmb004.flagtel.com [85.95.25.117]
    over a maximum of 30 hops:

    1 23 ms 27 ms 32 ms 10.9.240.80
    2 28 ms 37 ms 30 ms 220.224.183.137
    3 29 ms 29 ms 28 ms 220.224.183.142
    4 133 ms 148 ms 140 ms 115.255.252.57
    5 113 ms 130 ms 81 ms 62.216.147.73
    6 54 ms 52 ms 53 ms so-3-0-0.0.pjr02.mmb004.flagtel.com [85.95.25.11
    7]

    Trace complete.

    C:\Users\VikramHolla>tracert 85.95.25.233

    Tracing route to ge-1-1-0.0.pjr01.hkg005.flagtel.com [85.95.25.233]
    over a maximum of 30 hops:

    1 36 ms 27 ms 23 ms 10.9.240.80
    2 29 ms 28 ms 30 ms 220.224.183.137
    3 29 ms 29 ms 28 ms 220.224.183.142
    4 55 ms 56 ms 58 ms 115.255.252.57
    5 562 ms 397 ms 348 ms 62.216.147.73
    6 128 ms 140 ms 134 ms ge-1-1-0.0.pjr01.hkg005.flagtel.com [85.95.25.23
    3]

    Trace complete.

    C:\Users\VikramHolla>tracert 85.95.26.238

    Tracing route to 85.95.26.238 over a maximum of 30 hops

    1 73 ms * 152 ms 10.9.240.80
    2 91 ms 75 ms 115 ms 220.224.183.137
    3 28 ms 86 ms 91 ms 220.224.183.142
    4 189 ms 199 ms 137 ms 115.255.252.57
    5 58 ms 68 ms 60 ms 85.95.26.238

    Trace complete.

    C:\Users\VikramHolla>tracert 85.95.25.5

    Tracing route to xe-8-3-0.0.pjr03.mmb004.flagtel.com [85.95.25.5]
    over a maximum of 30 hops:

    1 23 ms 23 ms 27 ms 10.9.240.80
    2 40 ms 38 ms 39 ms 220.224.183.137
    3 29 ms 28 ms 28 ms 220.224.183.142
    4 169 ms 257 ms 218 ms 115.255.252.57
    5 165 ms 170 ms 141 ms 62.216.147.73
    6 54 ms 54 ms 53 ms xe-8-3-0.0.pjr03.mmb004.flagtel.com [85.95.25.5]


    Trace complete.

    C:\Users\VikramHolla>tracert 80.77.0.122

    Tracing route to 80.77.0.122 over a maximum of 30 hops

    1 23 ms 23 ms 22 ms 10.9.240.80
    2 103 ms 36 ms 28 ms 220.224.183.137
    3 86 ms 53 ms 28 ms 220.224.183.142
    4 55 ms 54 ms 58 ms 80.77.0.122

    Trace complete.

    C:\Users\VikramHolla>tracert 124.125.45.118

    Tracing route to VikramHolla-PC [124.125.45.118]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms VikramHolla-PC [124.125.45.118]

    Trace complete.

    C:\Users\VikramHolla>

  3. #1523
    Basic Member
    Join Date
    Nov 2012
    Posts
    2
    Quote Originally Posted by eclubmalaysia View Post
    Your location?
    Shanghai, China

  4. #1524
    Basic Member
    Join Date
    Oct 2012
    Posts
    1
    I'm also in China and having similar problems, and searching Chinese dota forums shows that it's pretty widespread... but I think the problem is really out of anything Valve could do for most of us over here.

    Since about three weeks ago, many ISPs around the country have been very agressively blocking UDP packets. Various programs I use, like mumble, my vpn for work, and other stuff all have to be run in a TCP mode to work as of late. The issue where you load into a game only to be faced with the "Too many reconnects" error or just an infinite loading screen, according to some other threads, is commonly caused by UDP packet loss... so this is just be putting two and two together but I think there's definitely a correlation here.

    Code:
    StartWatchingGame: Sending console command: connect 103.10.124.135:28074 0.0.0.0:28074
    NotifyClientSignon: 1
    Connecting to public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    44.035:  Sending UDP connect to public IP 103.10.124.135:28074
    44.035:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    50.485:  Sending UDP connect to public IP 103.10.124.135:28074
    50.485:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    56.919:  Sending UDP connect to public IP 103.10.124.135:28074
    56.919:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    62.921:  Sending UDP connect to public IP 103.10.124.135:28074
    62.921:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    68.924:  Sending UDP connect to public IP 103.10.124.135:28074
    68.924:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    74.926:  Sending UDP connect to public IP 103.10.124.135:28074
    74.926:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    80.962:  Sending UDP connect to public IP 103.10.124.135:28074
    80.962:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    86.981:  Sending UDP connect to public IP 103.10.124.135:28074
    86.981:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    92.983:  Sending UDP connect to public IP 103.10.124.135:28074
    92.983:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    98.985:  Sending UDP connect to public IP 103.10.124.135:28074
    98.985:  Sending UDP connect to private IP 0.0.0.0:28074
    
    Disconnect: Connection to the server exceeded the number of retries.
    Server is probably not available.
    For reference, here's my console from recently trying to watch a a game.
    Last edited by mkbao; 11-21-2012 at 09:49 AM.

  5. #1525
    Basic Member
    Join Date
    Mar 2012
    Posts
    3
    Me and my friends' ping have shot up to 150+ from the usual 80, can you check if there's any problem with the route?
    I am using Fastnet Indonesia
    My IP is: 118.137.180.6


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

    1 2 ms 2 ms 1 ms CISCO37087 [192.168.1.1]
    2 7 ms 25 ms 22 ms 10.58.192.1
    3 14 ms 15 ms 25 ms be4-cg03-pe03.fast.net.id [202.73.96.73]
    4 14 ms 90 ms 15 ms be4-cg03-pe03.fast.net.id [202.73.96.73]
    5 55 ms 24 ms 25 ms fm-dyn-111-95-246-86.fast.net.id [111.95.246.86]

    6 34 ms 27 ms 32 ms 203.208.192.153
    7 29 ms 43 ms 33 ms 203.208.166.201
    8 24 ms 38 ms 63 ms 203.208.166.238
    9 456 ms 151 ms 161 ms 203.208.152.177
    10 584 ms 812 ms 517 ms 63-218-211-21.static.pccwglobal.net [63.218.211.
    21]
    11 59 ms 77 ms 81 ms 63-218-211-21.static.pccwglobal.net [63.218.211.
    21]
    12 117 ms 128 ms 59 ms 63-218-211-21.static.pccwglobal.net [63.218.211.
    21]
    13 138 ms 115 ms 113 ms vlan905-an-cat6k-ts2-r1.starhub.net.sg [203.118.
    3.153]
    14 117 ms 123 ms 125 ms 203.116.6.238
    15 119 ms 117 ms 108 ms anatll10.starhub.net.sg [203.118.7.17]
    16 118 ms 119 ms 117 ms gw.sgp.valve.net [103.28.54.1]

    Trace complete.

    thanks before

  6. #1526
    Quote Originally Posted by beaver View Post
    Me and my friends' ping have shot up to 150+ from the usual 80, can you check if there's any problem with the route?
    I am using Fastnet Indonesia
    My IP is: 118.137.180.6


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

    1 2 ms 2 ms 1 ms CISCO37087 [192.168.1.1]
    2 7 ms 25 ms 22 ms 10.58.192.1
    3 14 ms 15 ms 25 ms be4-cg03-pe03.fast.net.id [202.73.96.73]
    4 14 ms 90 ms 15 ms be4-cg03-pe03.fast.net.id [202.73.96.73]
    5 55 ms 24 ms 25 ms fm-dyn-111-95-246-86.fast.net.id [111.95.246.86]
    6 34 ms 27 ms 32 ms 203.208.192.153
    7 29 ms 43 ms 33 ms 203.208.166.201
    8 24 ms 38 ms 63 ms 203.208.166.238
    9 456 ms 151 ms 161 ms 203.208.152.177
    10 584 ms 812 ms 517 ms 63-218-211-21.static.pccwglobal.net [63.218.211.21]
    11 59 ms 77 ms 81 ms 63-218-211-21.static.pccwglobal.net [63.218.211.21]
    12 117 ms 128 ms 59 ms 63-218-211-21.static.pccwglobal.net [63.218.211.21]
    13 138 ms 115 ms 113 ms vlan905-an-cat6k-ts2-r1.starhub.net.sg [203.118.3.153]
    14 117 ms 123 ms 125 ms 203.116.6.238
    15 119 ms 117 ms 108 ms anatll10.starhub.net.sg [203.118.7.17]
    16 118 ms 119 ms 117 ms gw.sgp.valve.net [103.28.54.1]
    Trace complete.
    thanks before
    The Trace is already symmetrical.

    [noc2@netmgt ~]$ trace 118.137.180.6
    traceroute to 118.137.180.6 (118.137.180.6), 30 hops max, 40 byte packets
    1 dsts1.starhub.net.sg (203.116.1.50) 12.191 ms 12.368 ms 12.356 ms
    2 vlan911-ancat6ktl2.starhub.net.sg (203.118.5.15) 0.442 ms 0.667 ms 0.662 ms
    3 anutli10.starhub.net.sg (203.118.3.228) 4.562 ms 4.560 ms 4.549 ms
    4 ten3-7.br01.hkg15.pccwbtn.net (63.218.211.117) 31.859 ms 33.407 ms 31.842 ms
    5 63-218-211-22.static.pccwglobal.net (63.218.211.22) 32.685 ms 34.376 ms 32.915 ms
    6 203.208.153.194 (203.208.153.194) 34.014 ms 203.208.153.198 (203.208.153.198) 33.443 ms 203.208.153.194 (203.208.153.194) 34.078 ms
    7 203.208.166.165 (203.208.166.165) 79.090 ms 203.208.166.237 (203.208.166.237) 66.237 ms 65.925 ms
    8 203.208.166.202 (203.208.166.202) 65.588 ms 203.208.152.230 (203.208.152.230) 65.566 ms 203.208.166.202 (203.208.166.202) 81.599 ms
    9 203.208.192.154 (203.208.192.154) 65.772 ms 65.779 ms 66.042 ms
    10 fm-dyn-111-95-247-105.fast.net.id (111.95.247.105) 67.264 ms 81.674 ms 80.365 ms
    11 fm-dyn-111-95-245-14.fast.net.id (111.95.245.14) 98.723 ms 83.751 ms 83.736 ms
    12 be8-pe04-cg03.fast.net.id (202.73.96.26) 78.678 ms 92.104 ms 79.150 ms
    13 * * *
    14 * * *

  7. #1527
    Quote Originally Posted by mkbao View Post
    I'm also in China and having similar problems, and searching Chinese dota forums shows that it's pretty widespread... but I think the problem is really out of anything Valve could do for most of us over here.

    Since about three weeks ago, many ISPs around the country have been very agressively blocking UDP packets. Various programs I use, like mumble, my vpn for work, and other stuff all have to be run in a TCP mode to work as of late. The issue where you load into a game only to be faced with the "Too many reconnects" error or just an infinite loading screen, according to some other threads, is commonly caused by UDP packet loss... so this is just be putting two and two together but I think there's definitely a correlation here.

    Code:
    StartWatchingGame: Sending console command: connect 103.10.124.135:28074 0.0.0.0:28074
    NotifyClientSignon: 1
    Connecting to public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    44.035:  Sending UDP connect to public IP 103.10.124.135:28074
    44.035:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    50.485:  Sending UDP connect to public IP 103.10.124.135:28074
    50.485:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    56.919:  Sending UDP connect to public IP 103.10.124.135:28074
    56.919:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    62.921:  Sending UDP connect to public IP 103.10.124.135:28074
    62.921:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    68.924:  Sending UDP connect to public IP 103.10.124.135:28074
    68.924:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    74.926:  Sending UDP connect to public IP 103.10.124.135:28074
    74.926:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    80.962:  Sending UDP connect to public IP 103.10.124.135:28074
    80.962:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    86.981:  Sending UDP connect to public IP 103.10.124.135:28074
    86.981:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    92.983:  Sending UDP connect to public IP 103.10.124.135:28074
    92.983:  Sending UDP connect to private IP 0.0.0.0:28074
    Retrying public(103.10.124.135:28074) private(0.0.0.0:28074) ...
    98.985:  Sending UDP connect to public IP 103.10.124.135:28074
    98.985:  Sending UDP connect to private IP 0.0.0.0:28074
    
    Disconnect: Connection to the server exceeded the number of retries.
    Server is probably not available.
    For reference, here's my console from recently trying to watch a a game.
    UDP connection is not GURANTEE. We cannot control UDP traffic over internet

  8. #1528
    Basic Member
    Join Date
    Nov 2012
    Posts
    30
    Hello eclub iam facing high ping problem again two days it was ok..from yesterday it started again ping goes 2000+ cant even play pls fix this problem man really cant even play...
    Here is my new trace route...

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

    C:\Users\VikramHolla>tracert 124.125.47.166

    Tracing route to VikramHolla-PC [124.125.47.166]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms VikramHolla-PC [124.125.47.166]

    Trace complete.

    C:\Users\VikramHolla>tracert 203.116.1.50

    Tracing route to dsts1.starhub.net.sg [203.116.1.50]
    over a maximum of 30 hops:

    1 22 ms 21 ms 42 ms 10.9.240.80
    2 27 ms 54 ms 76 ms 220.224.183.137
    3 26 ms 26 ms 32 ms 220.224.183.142
    4 47 ms 39 ms 38 ms 115.255.252.225
    5 43 ms 40 ms 52 ms 62.216.147.249
    6 73 ms 81 ms 73 ms so-7-0-0.0.ejr03.sin001.flagtel.com [62.216.128.
    73]
    7 * * * Request timed out.
    8 109 ms 118 ms 113 ms vlan905-an-cat6k-tl1.starhub.net.sg [203.118.3.1
    73]
    9 110 ms 143 ms 123 ms dsts1.starhub.net.sg [203.116.1.50]

    Trace complete.

    C:\Users\VikramHolla>tracert 203.118.7.14

    Tracing route to 203.118.7.14 over a maximum of 30 hops

    1 20 ms 22 ms 39 ms 10.9.240.80
    2 46 ms 28 ms 33 ms 220.224.183.137
    3 32 ms 26 ms 33 ms 220.224.183.142
    4 99 ms 38 ms 46 ms 115.255.252.225
    5 429 ms 338 ms 259 ms 62.216.147.249
    6 153 ms 143 ms 72 ms so-7-0-0.0.ejr03.sin001.flagtel.com [62.216.128.
    73]
    7 * * * Request timed out.
    8 112 ms 132 ms 103 ms 203.118.7.14

    Trace complete.

    C:\Users\VikramHolla>tracert 203.118.3.231

    Tracing route to anatli10.starhub.net.sg [203.118.3.231]
    over a maximum of 30 hops:

    1 145 ms 180 ms 227 ms 10.9.240.80
    2 108 ms 48 ms 45 ms 220.224.183.137
    3 134 ms 136 ms 139 ms 220.224.183.142
    4 39 ms 38 ms 57 ms 115.255.252.225
    5 52 ms 37 ms 37 ms 62.216.147.249
    6 95 ms 84 ms 73 ms so-7-0-0.0.ejr03.sin001.flagtel.com [62.216.128.
    73]
    7 104 ms 118 ms 104 ms anatli10.starhub.net.sg [203.118.3.231]

    Trace complete.

    C:\Users\VikramHolla>tracert 80.77.1.209

    Tracing route to 80.77.1.209 over a maximum of 30 hops

    1 38 ms 44 ms 37 ms 10.9.240.80
    2 111 ms 27 ms 38 ms 220.224.183.137
    3 403 ms 303 ms 195 ms 220.224.183.142
    4 682 ms 551 ms 710 ms 115.255.252.225
    5 436 ms 433 ms 574 ms 62.216.147.249
    6 525 ms 503 ms 465 ms 80.77.1.209

    Trace complete.

    C:\Users\VikramHolla>tracert 62.216.128.74

    Tracing route to so-5-1-0.0.ejr01.chn001.flagtel.com [62.216.128.74]
    over a maximum of 30 hops:

    1 351 ms 437 ms 418 ms 10.9.240.80
    2 493 ms 401 ms 370 ms 220.224.183.137
    3 738 ms 649 ms 560 ms 220.224.183.142
    4 412 ms 636 ms 683 ms 115.255.252.229
    5 432 ms 225 ms 298 ms 62.216.147.73
    6 493 ms 279 ms 451 ms so-5-1-0.0.ejr01.chn001.flagtel.com [62.216.128.
    74]

    Trace complete.

    C:\Users\VikramHolla>

  9. #1529
    Quote Originally Posted by Wizardsrus View Post
    Hello eclub iam facing high ping problem again two days it was ok..from yesterday it started again ping goes 2000+ cant even play pls fix this problem man really cant even play...
    Here is my new trace route...
    C:\Users\VikramHolla>
    You need to ask your ISP to choose the correct path.

  10. #1530
    Quote Originally Posted by Wizardsrus View Post
    I traced everything..Before i was getting 85 to 90 now 160+ i douno why. so pls see this problem and solve...
    Trace complete.

    C:\Users\VikramHolla>
    You need to ask your ISP to choose the correct path

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •