For the last 2 days when playing on a game hosted by someone living in S. America (SA Server) Ping has been 300-400 spiking into 1000-2000 frequently making it unplayable. Is there any ongoing problem or outage?
Normal ping of 200 is expected, not 400-2000
I live near California, and have 30ms on West server and 60ms on East Server
Thanks.
Hey there. There hasn’t been any known issues or reports so far with the latency in Diablo III, but it does sound like there’s some packet loss in the connection route when playing on the Latam Servers. Could you provide a WinMTR file to check out? Run the test until the problem occurs for 10 to 15 minutes. Copy and paste the text file created and paste it between two ~~~ like so:
~~~
WinMTR Here
~~~
If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)
Hey,
No latency problem on diablo 3 ?
i dont know on Latam servers but on european servers its laggy as well everyday
lag to the point where i get frozen in place… super lame and just about every 5 minutes… fix ur shteeee
Howdy NastyNova,
We aren’t aware of any widespread problems and most people seem to be playing without any problems. In this case, we need to gather some information so please follow the steps Caterpepi provided so we can get this further investigated.
I have consistent issues. Here’s my MTR
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 3 | 143 | 140 | 0 | 1 | 3 | 1 |
|cm-1-acr11.cosprings.co.denver.comcast.net - 0 | 154 | 154 | 9 | 15 | 30 | 11 |
|ae-251-1263-rur101.cosprings.co.denver.comcast.net - 0 | 154 | 154 | 10 | 16 | 36 | 13 |
| ae-23-ar01.denver.co.denver.comcast.net - 0 | 154 | 154 | 11 | 19 | 47 | 40 |
|be-36021-cs02.1601milehigh.co.ibone.comcast.net - 0 | 154 | 154 | 12 | 19 | 67 | 16 |
|be-1212-cr12.1601milehigh.co.ibone.comcast.net - 0 | 154 | 154 | 12 | 18 | 31 | 13 |
| be-304-cr02.dallas.tx.ibone.comcast.net - 0 | 154 | 154 | 25 | 32 | 46 | 36 |
|be-3312-pe12.1950stemmons.tx.ibone.comcast.net - 0 | 154 | 154 | 26 | 30 | 50 | 36 |
| 66.208.216.198 - 0 | 154 | 154 | 26 | 36 | 75 | 38 |
| ae1-br02-eqda6.as57976.net - 0 | 154 | 154 | 49 | 57 | 144 | 58 |
| et-0-0-2-br02-swlv10.as57976.net - 0 | 154 | 154 | 50 | 58 | 153 | 57 |
| 137.221.65.122 - 0 | 142 | 142 | 100 | 719 | 1540 | 747 |
| No response from host - 100 | 31 | 0 | 0 | 0 | 0 | 0 |
| 137.221.68.77 - 0 | 154 | 154 | 49 | 56 | 118 | 52 |
| 24.105.30.129 - 0 | 154 | 154 | 48 | 53 | 64 | 50 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
137.221.65.122 is consistently showing latency spikes often over 1s.
137.221.65.122 is a Blizzard peering address. The network equipment at Blizzard’s network edge / internal network will be configured to drop / de-prioritise ICMP traffic (the type of network packs that PING / TRACERT uses) so slow response times there don’t necessarily indicate there’d be an issue with game traffic.
However, you are getting 3% packet loss at 10.0.0.1 and that’s an internal address, i.e. probably your PC’s network card. Reset the network equipment and your PC. If you’re playing wirelessly and could use wired, do that. If you’re wired, swap the Ethernet cable to one of the other ports in the router to rule out issues with the router’s port. If you have a spare Ethernet cable, use that to rule out issues with the cable.
Good point, I missed the packet drops on my own network. Almost brand new motherboard, wired, but problem could be in cable, or router, or cable modem, so I will have to troubleshoot. Thank you sir.
I ran more tests where I did not have local packet loss. Last night I was doing ok for smoothness of game play. So maybe it’s not that one hop. My girlfriend was having similar issues in Diablo, so I thought maybe there was common point of congestion.