Diablo® III

persisting high latency, unplayable

so it's been 5 days now of constant high latency. i kept checking isp speed and it's the same as day 1 when i got it.

my normal latency is 210-220ms, will go up to 250ms+ but will go back down to normal.

now it's normal 250ms then go up to 300ms+

then it's 350ms+

what is wrong, blizz??
Reply Quote
5 mins of play using tracert

http://imgur.com/RFWiyBb

http://imgur.com/xTOe6ou

philippines here so asia

please help blizz
Edited by pichapie#6783 on 6/14/2013 10:30 PM PDT
Reply Quote
need to know what's wrong here, blizz.
Reply Quote
Shut down any unnecessary programs. If torrenting or downloading movies, youtube, or whatever, shut those down too. Check for windows updates etc, then reboot. If problem persists, check for malware.
Reply Quote
thanks silver. any reliable anti malware programs you could suggest? :D
Reply Quote
06/14/2013 11:51 PMPosted by pichapie
thanks silver. any reliable anti malware programs you could suggest? :D


malwarebytes is a good program
http://www.malwarebytes.org/products/

also i would suggest on future traces do not cut out all the hop names like you did. i realize hop 0-1 may show your IP address, so cutting those out is completely understandable. however, if you cut out all of those hops its hard to tell if its your ISP or not since you also deleted all the IP addresses.
Edited by Morogoth#1321 on 6/15/2013 12:15 AM PDT
Reply Quote
oh my bad. i'll make one again
Reply Quote
http://imgur.com/BFvMvaE

http://imgur.com/ok1sg13
Reply Quote
It would be better if you did as described here;
  • https://eu.battle.net/support/en/article/496
  • https://eu.battle.net/support/en/article/718

  • While it's mostly just the same information presented differently, it's probably worth using the tools which the employees have been trained in. Just my $0.02.
    Reply Quote
    tracert showed this

    2 53 ms 53 ms 53 ms 112.200.0.1.pldt.net [112.200.0.1]

    3 53 ms 54 ms 53 ms 122.2.135.185.pldt.net [122.2.135.185]

    4 55 ms 55 ms 55 ms 210.213.131.70.static.pldt.net [210.213.131.70]

    5 54 ms 53 ms 53 ms 210.213.131.93.static.pldt.net [210.213.131.93]

    6 210 ms 210 ms 209 ms 129.250.197.1

    7 210 ms 210 ms 210 ms ae-4.r07.snjsca04.us.bb.gin.ntt.net [129.250.4.119]

    8 215 ms 216 ms 215 ms 192.205.37.57

    9 299 ms 297 ms 302 ms cr1.sffca.ip.att.net [12.122.114.30]

    10 297 ms 304 ms 303 ms cr1.la2ca.ip.att.net [12.122.3.122]

    11 299 ms 299 ms 298 ms gar20.la2ca.ip.att.net [12.122.128.181]

    12 307 ms 502 ms 304 ms 12.122.251.190

    13 298 ms 302 ms 301 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]

    14 * * * Request timed out.

    15 * * * Request timed out.

    16 * * * Request timed out.

    17 * * * Request timed out.

    18 * * * Request timed out.

    19 * * * Request timed out.

    20 * * * Request timed out.

    21 * * * Request timed out.

    22 * * * Request timed out.

    23 * * * Request timed out.

    24 * * * Request timed out.

    25 * * * Request timed out.

    26 * * * Request timed out.

    27 * * * Request timed out.

    28 * * * Request timed out.

    29 * * * Request timed out.

    30 * * * Request timed out.
    Reply Quote
    2 112.200.0.1.pldt.net [112.200.0.1]

    3 122.2.135.185.pldt.net [122.2.135.185]

    4 210.213.131.70.static.pldt.net [210.213.131.70]

    5 210.213.131.93.static.pldt.net [210.213.131.93]

    6 129.250.197.1

    7 ae-4.r07.snjsca04.us.bb.gin.ntt.net [129.250.4.119]

    8 192.205.37.57

    9 cr1.sffca.ip.att.net [12.122.114.30]

    10 cr1.la2ca.ip.att.net [12.122.3.122]

    11 gar20.la2ca.ip.att.net [12.122.128.181]

    12 12-122-254-238.attens.net [12.122.254.238]

    13 mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]

    14 * * *

    Computing statistics for 350 seconds...

    Source to Here This Node/Link

    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

    2 52ms 0/ 100 = 0% 0/ 100 = 0% 112.200.0.1.pldt.net [112.200.0.1]

    0/ 100 = 0% |

    3 53ms 0/ 100 = 0% 0/ 100 = 0% 122.2.135.185.pldt.net [122.2.135.185]

    0/ 100 = 0% |

    4 53ms 0/ 100 = 0% 0/ 100 = 0% 210.213.131.70.static.pldt.net [210.213.131.70]

    0/ 100 = 0% |

    5 55ms 0/ 100 = 0% 0/ 100 = 0% 210.213.131.93.static.pldt.net [210.213.131.93]

    0/ 100 = 0% |

    6 244ms 0/ 100 = 0% 0/ 100 = 0% 129.250.197.1

    0/ 100 = 0% |

    7 253ms 0/ 100 = 0% 0/ 100 = 0% ae-4.r07.snjsca04.us.bb.gin.ntt.net [129.250.4.119]

    0/ 100 = 0% |

    8 249ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.57

    100/ 100 =100% |

    9 --- 100/ 100 =100% 0/ 100 = 0% cr1.sffca.ip.att.net [12.122.114.30]

    0/ 100 = 0% |

    10 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.122.3.122]

    0/ 100 = 0% |

    11 --- 100/ 100 =100% 0/ 100 = 0% gar20.la2ca.ip.att.net [12.122.128.181]

    0/ 100 = 0% |

    12 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-238.attens.net [12.122.254.238]

    0/ 100 = 0% |

    13 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]

    0/ 100 = 0% |

    14 --- 100/ 100 =100% 0/ 100 = 0% my_pc [0.0.0.0]
    Reply Quote
    bump. really need help on this
    Reply Quote
    It would be better if you did as described here;
  • https://eu.battle.net/support/en/article/496
  • https://eu.battle.net/support/en/article/718

  • While it's mostly just the same information presented differently, it's probably worth using the tools which the employees have been trained in. Just my $0.02.


    while those work for basic information purposes they are very lacking.
    you can see that D3TR traces constantly for as long as you want it to. this by itself makes it better.

    besides this point.. did you know that support does actually suggest D3TR?
    its been reported from users stating ticket support does this.
    ..but if you need more proof. check out that post there.
    http://us.battle.net/d3/en/forum/topic/5235707967#14

    anyway...
    for the OP the data reposted shows exactly the same kind of thing as the D3TR did. its just taken over a short period of time rather then continuously run. it shows your latency spikes after you get to the blizz servers.
    edit:
    according to the trace the IP [129.250.197.1] is where the problems with latency start. that is owned by "NTT America, Inc.". so it is not your ISP that is the problem. given that the latency appears to start before the blizzard network i would say its not blizzard. you are suffering from the connections between your network and blizz network not being all that great imo.
    Edited by Morogoth#1321 on 6/15/2013 5:20 PM PDT
    Reply Quote
    thanks for clearing it up, morogoth :D

    i'll play the waiting game. blizz help :D
    Reply Quote

    Please report any Code of Conduct violations, including:

    Threats of violence. We take these seriously and will alert the proper authorities.

    Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

    Harassing or discriminatory language. This will not be tolerated.

    Forums Code of Conduct

    Report Post # written by

    Reason
    Explain (256 characters max)
    Submit Cancel

    Reported!

    [Close]