Tracert, 50k ping and disconnections

ursomimao
ursomimao Posts: 26 Arc User
edited April 2015 in Support Desk
For the last couple of weeks I have noticed huge ping (20k to 50k) and disconnections and the number of these ocurrences is increasing more and more everyday, today I was lucky to be able to play for around 1 hour and a half without this problem. I play at dreamweaver server and I sent a ticket already with lots of information they asked for, but the "time out" showed by this tracert was appointed as the culprit and I was asked to talk to my ISP help desk... I did, they said there was nothing wrong on their end. Is there anything else I can do about it? (I don't really know how to interprete this tracert info, so any explanation would be appreciated)
Thanks in advance.


Tracing route to pwieast1.perfectworld.com [198.49.243.15]
over a maximum of 30 hops:

1 7 ms 3 ms 1 ms PowerBox.home [192.168.25.1]
2 8 ms 8 ms 8 ms gvt-b-se01.pae.gvt.net.br [187.115.211.223]
3 9 ms 8 ms 9 ms 179.184.83.101.dynamic.adsl.gvt.net.br [179.184.
83.101]
4 12 ms 17 ms 9 ms gvt-te-0-2-0-1.rc02.pae.gvt.net.br [189.59.252.2
13]
5 25 ms 21 ms 22 ms gvt-te-0-15-0-5.rc03.cta.gvt.net.br [177.99.251.
14]
6 28 ms 25 ms 27 ms gvt-te-0-6-0-12.rc04.spo.gvt.net.br [179.185.130
.178]
7 26 ms 30 ms 27 ms gvt-te-0-0-0-4.rt01.spo.gvt.net.br [189.59.248.6
1]
8 69 ms 25 ms 25 ms xe-1-0-2.ar4.gru1.gblx.net [64.214.145.49]
9 133 ms 132 ms 132 ms po3-20G.ar2.MIA2.gblx.net [67.16.139.18]
10 137 ms 137 ms 139 ms te0-0-0-34.ccr21.mia03.atlas.cogentco.com [154.5
4.12.69]
11 133 ms 133 ms 134 ms be2055.ccr22.mia01.atlas.cogentco.com [154.54.24
.233]
12 146 ms 145 ms 147 ms be2123.ccr42.atl01.atlas.cogentco.com [154.54.24
.197]
13 153 ms 152 ms 152 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31
.110]
14 153 ms 154 ms 151 ms be2151.ccr42.jfk02.atlas.cogentco.com [154.54.40
.74]
15 157 ms 159 ms 164 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
16 158 ms 157 ms 158 ms te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.130]
17 221 ms 209 ms 159 ms 38.111.40.114
18 * * * Request timed out.
19 158 ms 157 ms 160 ms 198.49.243.15

Trace complete.
Post edited by Unknown User on

Comments

  • NRGLG - Heavens Tear
    NRGLG - Heavens Tear Posts: 393 Arc User
    edited April 2015
    Hop 9 is where a minor problem starts (probably just a long distance). Hop 18 is PWI's ISP, who is not having issues. They implemented a DDoS mitigation system, so it will not return ping replies, ping TTL expired, TCP ACKs, or otherwise. That results in the "Request timed out" message.

    From the trace route you've given, there appears to be no problems. Make sure when doing a trace route next time that it is during a period when you are having problems. Taking it when you are not having issues is not going to tell us anything.
    Kernal32.dll error? Get Arc XP for PWI because PWE Derpped -->http://www.nrgs.org/dev/arcxp/ArcXP.zip<-- (Don't select the arrows!)

    Forums. Where opinion is truth, truth are facts, facts are wrong, and wrong is an opinion.

    My site: >http://nrgs.org&lt; | Free and open source tools and utilities developed by me
  • ursomimao
    ursomimao Posts: 26 Arc User
    edited April 2015
    Thank so much for the info provided. One more detail, not sure if it's relevant, but I noticed the issues are ocurring today at the same time as yesterday. I ran the tracert at the time of the issue, it seemed very similar to the previous one, so I guess no issue there according to what you said. But I also ran a ping test, and got that result, which was different from when the game was running ok (there were no packages lost while thew game was running ok, untill the issue reocorred today). Any comments about it?
    Thanks again.

    Tracing route to pwieast1.perfectworld.com [198.49.243.15]
    over a maximum of 30 hops:

    1 1 ms 4 ms 1 ms PowerBox.home [192.168.25.1]
    2 12 ms 8 ms 10 ms gvt-b-se01.pae.gvt.net.br [187.115.211.223]
    3 8 ms 9 ms 8 ms 179.184.83.101.dynamic.adsl.gvt.net.br [179.184.
    83.101]
    4 19 ms 9 ms 14 ms gvt-te-0-2-0-1.rc02.pae.gvt.net.br [189.59.252.2
    13]
    5 24 ms 19 ms 22 ms gvt-te-0-7-0-10.rc03.cta.gvt.net.br [189.59.253.
    165]
    6 31 ms 27 ms 29 ms gvt-te-0-4-0-10.rc04.spo.gvt.net.br [179.185.130
    .162]
    7 46 ms 27 ms 30 ms gvt-te-0-0-0-4.rt01.spo.gvt.net.br [189.59.248.6
    1]
    8 25 ms 27 ms 25 ms 67.17.196.193
    9 161 ms 138 ms 137 ms te0-0-0-34.ccr21.mia03.atlas.cogentco.com [154.5
    4.12.69]
    10 143 ms 142 ms 139 ms be2054.ccr21.mia01.atlas.cogentco.com [154.54.80
    .41]
    11 156 ms 155 ms 145 ms be2122.ccr41.atl01.atlas.cogentco.com [154.54.24
    .193]
    12 161 ms 165 ms 164 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.31
    .106]
    13 151 ms 165 ms 163 ms be2518.ccr41.jfk02.atlas.cogentco.com [154.54.80
    .161]
    14 187 ms 176 ms 198 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
    .14]
    15 160 ms 161 ms 162 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
    om [154.54.46.134]
    16 162 ms 158 ms 169 ms 38.111.40.114
    17 * * * Request timed out.
    18 162 ms 160 ms 162 ms 198.49.243.15

    Trace complete.

    Pinging pwieast1.perfectworld.com [198.49.243.15] with 32 bytes of data:
    Request timed out.
    Reply from 198.49.243.15: bytes=32 time=215ms TTL=48
    Request timed out.
    Request timed out.

    Ping statistics for 198.49.243.15:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 215ms, Maximum = 215ms, Average = 215ms
  • SylenThunder - Twilight Temple
    SylenThunder - Twilight Temple Posts: 7,908
    edited April 2015
    Again, hop 9 is where you see your latency spike. Probably a lot of traffic hitting that node at that particular time of day. PPL getting home from work, ect.
    [SIGPIC][/SIGPIC]
  • ursomimao
    ursomimao Posts: 26 Arc User
    edited April 2015
    Thanks for the answer. PWI support also replied and the only thing I can do now is to make my ISP aware of the issue and hope the ISPs along the way (particularly the one related to hop 9) can make something that would improve my connection.
    Thank you so much for all the information.

Categories