Erazer,
I spoke to Araxom about this issue, and I looked at the reddit thread. The tracerts posted show that the issue may be starting from the lost data seen in hop 7. Hop 7 is outside of our network, so you may need to contact your ISP to have them look into this for you.
First though, let's download WinMTR. This tool will run a different style of pathping which will hopefully give us a little bit more information about what might be going on with the connection.
1. Download WinMTR
2. Unzip the WinMTR.zip file to the Desktop.
3. Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows.
4. Run the WinMTR.exe
5. Type the IP address you want to trace in the "Host" field. If you are not sure what IP address to use, be sure to check out our "Running A Pathping Test" support article, which mentions all of our IPs used for troubleshooting purposes.
6. Click on "Start" and then launch the game. Once you notice the connection issue, play for about 10 more minutes, minimize the game and click on "Stop".
7. Click on "Copy text to clipboard" and paste the results into your next forum reply.
______________________________________________________
I'm available Sunday through Thursday from 11AM to 8PM Pacific Time
Support Contact Information
Got some feedback?
 | Lag Spikes on NA Diablo 3 servers(1) | Category: Technical SupportSeptember-8-2014 1:15 PM PDT (8 years ago)  |
| I was told to post here http://www.reddit.com/r/Diablo/comments/2ftxqj/bad_lag_on_na_servers_careful_with_hc/ 
#2
9/8/2014
I am having the exact same issues - my lag spikes have been going on since last night and make the game entirely unplayable. I did what you suggested above and here is my data:
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 10.0.1.1 - 0 | 572 | 572 | 0 | 0 | 1 | 0 | | c-98-225-232-1.hsd1.nj.comcast.net - 7 | 458 | 430 | 9 | 40 | 2022 | 20 | | 68.86.213.5 - 5 | 480 | 457 | 7 | 24 | 930 | 14 | |ae-20-0-ar03.newcastle.de.panjde.comcast.net - 5 | 492 | 472 | 8 | 24 | 924 | 10 | |pos-5-14-0-0-cr01.ashburn.va.ibone.comcast.net - 6 | 476 | 452 | 12 | 27 | 800 | 18 | |he-0-15-0-0-cr01.350ecermak.il.ibone.comcast.net - 5 | 484 | 462 | 11 | 28 | 928 | 19 | | 192.205.37.41 - 5 | 492 | 472 | 14 | 31 | 932 | 18 | | cr2.wswdc.ip.att.net - 8 | 436 | 402 | 79 | 93 | 996 | 88 | | cr1.cgcil.ip.att.net - 7 | 460 | 432 | 80 | 96 | 865 | 88 | | cr2.dvmco.ip.att.net - 7 | 460 | 432 | 79 | 92 | 452 | 90 | | cr1.slkut.ip.att.net - 7 | 448 | 417 | 79 | 96 | 867 | 91 | | cr2.la2ca.ip.att.net - 7 | 452 | 422 | 81 | 97 | 999 | 93 | | gar5.lsrca.ip.att.net - 7 | 456 | 427 | 78 | 103 | 1090 | 90 | | 12.122.251.186 - 8 | 440 | 407 | 79 | 101 | 865 | 84 | |mdf001c7613r0004-gig-12-1.lax1.attens.net - 7 | 448 | 417 | 79 | 101 | 993 | 112 | | 12.129.209.68 - 7 | 460 | 432 | 79 | 90 | 448 | 86 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Heya, i would like to also post similar data, i notice that i will have to talk with my isp as a couple hops are their fault, but sadly the main culprit, Telia, is out of my league apparently.
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | lms-02-lo66.bras.cantv.net - 0 | 664 | 664 | 26 | 30 | 231 | 29 | | lms-02-lo66.bras.cantv.net - 0 | 664 | 664 | 26 | 30 | 198 | 29 | | 172.16.36.1 - 4 | 577 | 555 | 26 | 37 | 389 | 31 | | 10.150.0.161 - 5 | 565 | 540 | 29 | 34 | 234 | 32 | | 10.150.0.97 - 4 | 577 | 555 | 28 | 34 | 182 | 33 | | 10.150.0.202 - 0 | 664 | 664 | 28 | 33 | 175 | 30 | | mai-b2-link.telia.net - 9 | 501 | 460 | 157 | 284 | 471 | 306 | | mai-b1-link.telia.net - 5 | 526 | 503 | 122 | 373 | 2886 | 173 | | att-ic-156318-mai-b1.c.telia.net - 1 | 660 | 659 | 126 | 166 | 307 | 177 | | 12.122.155.170 - 5 | 573 | 550 | 188 | 226 | 379 | 243 | | cr2.ormfl.ip.att.net - 0 | 664 | 664 | 183 | 226 | 415 | 237 | | cr1.ormfl.ip.att.net - 0 | 664 | 664 | 189 | 226 | 418 | 239 | | cr2.hs1tx.ip.att.net - 0 | 664 | 664 | 180 | 227 | 413 | 242 | | cr1.dlstx.ip.att.net - 1 | 660 | 659 | 192 | 226 | 466 | 237 | | cr2.dlstx.ip.att.net - 5 | 572 | 549 | 187 | 226 | 395 | 237 | | cr2.la2ca.ip.att.net - 0 | 664 | 664 | 182 | 228 | 420 | 243 | | 12.123.132.209 - 0 | 664 | 664 | 179 | 233 | 446 | 315 | | 12.122.251.186 - 1 | 653 | 650 | 184 | 231 | 435 | 240 | |mdf001c7613r0004-gig-12-1.lax1.attens.net - 0 | 664 | 664 | 188 | 230 | 438 | 236 | | 12.129.209.68 - 3 | 601 | 585 | 186 | 224 | 379 | 240 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Did a pathping from the Tacoma area just now. It appears there's some small amount of latency with Comcast, and after you pass their network, AT&T becomes the major issue with as much as 93% loss.
Sorry about the code tags, it was the only way the forums would present this in a readable format for some reason. Going to try the WinMTR process next to see if it gets you any better data to work with. At this point the disconnects are so bad I can't even complete one set of bounties without being bounced. Just got booted after killing the boss for a cursed shrine, watched the loot drop, and got the 'you have been disconnected' message. Couldn't even pick up the shiny legendary staring back at me LOL. Tracing route to 12.129.209.68 over a maximum of 30 hops
Same issue, extreme lag spikes. Sometimes I can cast abilities and see resources go down, but my character can't move, just jitters the screen running in place. Other times I can run around but combat freezes and suddenly catches up with rubberband style damage etc. Followed the steps you posted for the OP, seem to lose a lot of packets when making the regional swap with comcast, and then steady packet loss amounts throughout the AT&T portion of the connection...? Kinda weird though that three of us in this thread alone with different regional Comcast services are experiencing issues? New Jersey, Washington, and Florida? I blame Comcast's horrible network track record.
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | MATTHEWS-TIME-C - 1 | 201 | 199 | 0 | 2 | 33 | 1 | | 174.63.152.1 - 4 | 182 | 176 | 10 | 52 | 3495 | 25 | |te-7-1-ur02.leecocourt.fl.naples.comcast.net - 3 | 190 | 186 | 8 | 50 | 4442 | 11 | |te-0-9-0-3-ar03.venice.fl.westfl.comcast.net - 5 | 177 | 169 | 12 | 32 | 1421 | 17 | |pos-0-2-0-0-cr01.56marietta.ga.ibone.comcast.net - 4 | 181 | 175 | 24 | 67 | 4489 | 51 | | No response from host - 100 | 42 | 0 | 0 | 0 | 0 | 0 | |as7018-pe01.56marietta.ga.ibone.comcast.net - 12 | 144 | 128 | 25 | 101 | 4465 | 30 | | cr1.attga.ip.att.net - 13 | 140 | 123 | 74 | 144 | 4527 | 78 | | cr2.dlstx.ip.att.net - 10 | 151 | 137 | 74 | 154 | 4525 | 80 | | cr2.la2ca.ip.att.net - 11 | 147 | 132 | 73 | 157 | 4524 | 82 | | 12.123.132.209 - 13 | 140 | 123 | 74 | 159 | 4532 | 75 | | 12-122-254-230.attens.net - 15 | 129 | 110 | 73 | 201 | 4529 | 75 | | 206.16.68.50 - 12 | 144 | 128 | 72 | 150 | 4519 | 78 | | 12.129.209.68 - 10 | 151 | 137 | 71 | 151 | 4526 | 79 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Haven't been disconnected in over an hour, but latency is still 2x-5x normal, with frequent spikes and rubberbanding.
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | - 0 | 9878 | 9878 | 0 | 0 | 19 | 0 | | 10.0.0.1 - 0 | 9880 | 9880 | 0 | 1 | 20 | 1 | | 73.102.132.1 - 6 | 8179 | 7752 | 8 | 14 | 55 | 15 | |te-0-0-0-6-ur05.tacoma.wa.seattle.comcast.net - 6 | 8227 | 7813 | 9 | 15 | 53 | 14 | |ae-28-0-ar03.burien.wa.seattle.comcast.net - 6 | 8091 | 7643 | 9 | 15 | 56 | 15 | |ae-28-0-ar03.seattle.wa.seattle.comcast.net - 6 | 8179 | 7753 | 11 | 17 | 55 | 15 | |he-1-3-0-0-10-cr01.seattle.wa.ibone.comcast.net - 6 | 8211 | 7793 | 11 | 19 | 62 | 18 | | be-11-pe03.seattle.wa.ibone.comcast.net - 5 | 8255 | 7848 | 11 | 17 | 85 | 13 | | as7018.seattle.wa.ibone.comcast.net - 5 | 8247 | 7837 | 11 | 35 | 267 | 18 | | cr82.st0wa.ip.att.net - 6 | 8178 | 7752 | 37 | 45 | 84 | 40 | | cr2.ptdor.ip.att.net - 6 | 8127 | 7687 | 36 | 45 | 111 | 46 | | 12.122.2.74 - 6 | 8031 | 7567 | 37 | 44 | 92 | 47 | | cr2.la2ca.ip.att.net - 6 | 8175 | 7748 | 37 | 46 | 134 | 43 | | 12.123.132.209 - 6 | 8199 | 7778 | 36 | 53 | 303 | 39 | | 12.122.251.186 - 6 | 8199 | 7778 | 36 | 50 | 384 | 60 | | 206.16.68.50 - 6 | 8107 | 7663 | 36 | 49 | 425 | 41 | | 12.129.209.68 - 6 | 8195 | 7772 | 37 | 43 | 83 | 48 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Same issue here since last tuesday or wednesday, located in Quebec Canada. I'll do the WinMTR tomorrow and post the results here.
I'm having the same issue. I go from typical 100ms ping or so to 500ms that only lasts a few seconds every 30 seconds or so. Ill vault on my DH and get taken back to where I was.
Here is my WinMTR: |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 1 | 819 | 812 | 0 | 174 | 711 | 168 | | L100.BLTMMD-VFTTP-59.verizon-gni.net - 1 | 831 | 827 | 12 | 192 | 719 | 115 | | G0-2-0-2.BLTMMD-LCR-22.verizon-gni.net - 1 | 819 | 812 | 8 | 185 | 719 | 124 | | ae20-0.PHIL-BB-RTR1.verizon-gni.net - 1 | 835 | 832 | 10 | 180 | 605 | 106 | | No response from host - 100 | 170 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 170 | 0 | 0 | 0 | 0 | 0 | | 0.ae1.BR1.IAD8.ALTER.NET - 1 | 815 | 807 | 16 | 191 | 621 | 196 | | 192.205.36.137 - 1 | 823 | 817 | 14 | 192 | 726 | 173 | | cr82.wshdc.ip.att.net - 1 | 823 | 817 | 82 | 257 | 680 | 216 | | cr2.wswdc.ip.att.net - 1 | 815 | 807 | 82 | 257 | 676 | 266 | | cr1.cgcil.ip.att.net - 1 | 815 | 807 | 82 | 258 | 771 | 256 | | cr2.dvmco.ip.att.net - 1 | 819 | 812 | 84 | 261 | 697 | 278 | | cr1.slkut.ip.att.net - 1 | 827 | 822 | 82 | 257 | 712 | 274 | | cr2.la2ca.ip.att.net - 1 | 827 | 822 | 85 | 258 | 725 | 276 | | gar5.lsrca.ip.att.net - 1 | 819 | 812 | 81 | 268 | 703 | 218 | | 12.122.251.186 - 2 | 807 | 797 | 79 | 258 | 723 | 142 | |mdf001c7613r0003-gig-10-1.lax1.attens.net - 1 | 819 | 812 | 79 | 260 | 698 | 81 | | paxonix-placeholder.lax1.attens.net - 2 | 811 | 802 | 81 | 254 | 687 | 264 | | 12.129.209.68 - 1 | 819 | 812 | 81 | 253 | 691 | 253 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Aaaaand now we're back to the disconnects.
|------------------------------------------------------------------------------------------|
| WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 68.55.132.1 - 10 | 445 | 402 | 8 | 13 | 47 | 12 | | 69.139.214.113 - 10 | 453 | 412 | 7 | 13 | 77 | 10 | |ae-22-0-ar04.whitemarsh.md.bad.comcast.net - 11 | 437 | 392 | 9 | 18 | 105 | 9 | |he-3-2-0-0-11-cr01.newyork.ny.ibone.comcast.net - 9 | 457 | 417 | 14 | 20 | 60 | 19 | | No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 | | 192.205.37.33 - 9 | 457 | 417 | 14 | 21 | 56 | 17 | | cr1.n54ny.ip.att.net - 10 | 445 | 402 | 78 | 84 | 120 | 84 | | cr2.cgcil.ip.att.net - 9 | 457 | 417 | 78 | 85 | 188 | 84 | | cr1.cgcil.ip.att.net - 10 | 449 | 407 | 78 | 84 | 155 | 85 | | cr2.dvmco.ip.att.net - 9 | 461 | 422 | 79 | 86 | 160 | 86 | | cr1.slkut.ip.att.net - 11 | 437 | 392 | 0 | 86 | 124 | 87 | | cr2.la2ca.ip.att.net - 10 | 453 | 412 | 0 | 85 | 137 | 86 | | gar5.lsrca.ip.att.net - 11 | 429 | 382 | 0 | 93 | 244 | 79 | | 12.122.251.186 - 10 | 453 | 412 | 0 | 94 | 305 | 110 | | 206.16.68.42 - 12 | 425 | 377 | 0 | 93 | 307 | 79 | | paxonix-placeholder.lax1.attens.net - 10 | 441 | 397 | 0 | 84 | 118 | 82 | | 12.129.209.68 - 10 | 445 | 402 | 78 | 84 | 118 | 83 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider The fun part is the pass the buck, on everything. I have contacted my ISP and they sent a tech out which did nothing. So I'm in the process of building up a case till they find a real solution to the problem. Not sure if blizzard talking to whoever or where ever the issue is, may produce better results. Since most ISPs really don't care about the individual vs. everyone else.
AT&T becomes the major issue with as much as 93% loss. That is not packet loss on AT&T. That is due to server masking for security reasons and should actually say 100% unless there is loss before the AT&T servers, They cover that in the article on how to perform and read a Blizzard pathping. Your packet loss starts between hop 2 and 3 and gets passed on forward from there. Most of these posts have packet loss early on :( Varena...yours is really odd. You should be going from whitemarsh to VA, not NY and you have a lot of packet loss starting with your first reported hops. guessing you removed your home network.
I tried all the blizzard solutions, even direct connecting to the modem and using a completely different PC, the issue persists and happens in WoW as well. However the problem is not always continuous occasionally I've played for hours with out anything negative happening connection wise. Recently as in tonight starting around 1:30 am I can't join a game with out issues or stay connected for more than 10 minutes before getting disconnected from my game, logged out of D3, or kicked off the b.net loader. Before that I played WoW for 3 hours with no MS spikes or lag of any kind. Outside of the routing issue, it's clearly not congestion at 1-5:30 am est. Seems like a hardware issue somewhere along the line. Good luck attempting to get anyone to do jack squat about that, though. Non-blizzard related stuff like Steam has no issues.
[Post edited one time, last edit by Felgarion#1848 at September-9-2014 2:22 AM PDT (8 years ago)] | ||
| Lag Spikes on NA Diablo 3 servers(2) | September-8-2014 1:42 PM PDT (8 years ago) |
| Erazer, I spoke to Araxom about this issue, and I looked at the reddit thread. The tracerts posted show that the issue may be starting from the lost data seen in hop 7. Hop 7 is outside of our network, so you may need to contact your ISP to have them look into this for you. First though, let's download WinMTR. This tool will run a different style of pathping which will hopefully give us a little bit more information about what might be going on with the connection. 1. Download WinMTR 2. Unzip the WinMTR.zip file to the Desktop. 3. Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows. 4. Run the WinMTR.exe 5. Type the IP address you want to trace in the "Host" field. If you are not sure what IP address to use, be sure to check out our "Running A Pathping Test" support article, which mentions all of our IPs used for troubleshooting purposes. 6. Click on "Start" and then launch the game. Once you notice the connection issue, play for about 10 more minutes, minimize the game and click on "Stop". 7. Click on "Copy text to clipboard" and paste the results into your next forum reply. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
