(4/27) North America - Midwest Latency Collection Thread - Diablo III Blue Post

Also in the Midwest (Madison, WI), also having the same issue. I can barely even log into the game half the time. This just started today when I got home from work, ready to play some D3 :(

Tracing route to 12.129.209.26 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms [192.168.1.1]
2 * * * Request timed out.
3 11 ms 11 ms 12 ms dtr01ftbgwi-tge-0-6-0-3.ftbg.wi.charter.com [96.
34.25.58]
4 13 ms 16 ms 14 ms crr01ftbgwi-bue-4.ftbg.wi.charter.com [96.34.18.
108]
5 19 ms 14 ms 16 ms crr01euclwi-bue-1.eucl.wi.charter.com [96.34.16.
77]
6 19 ms 15 ms 15 ms bbr01euclwi-bue-4.eucl.wi.charter.com [96.34.2.4
]
7 * 22 ms 21 ms 10-2-15.ear2.Chicago2.Level3.net [4.15.84.21]
8 21 ms 19 ms 23 ms 192.205.37.149
9 86 ms 84 ms 77 ms cr1.cgcil.ip.att.net [12.122.133.34]
10 79 ms 72 ms 72 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 72 ms 75 ms 74 ms cr1.slkut.ip.att.net [12.122.30.25]
12 88 ms 89 ms 96 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 94 ms 90 ms 93 ms gar5.lsrca.ip.att.net [12.122.85.33]
14 74 ms 75 ms 76 ms 12-122-254-230.attens.net [12.122.254.230]
15 295 ms * * 206.16.68.42
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * *

[Post edited one time, last edit by MrMoose#1443 at April-27-2015 3:56 PM PDT (10 years ago)]

Alootrinn #1794	(4/27) North America - Midwest Latency Collection Thread (1)	Category: Technical SupportApril-27-2015 3:34 PM PDT (10 years ago)
	I live in the midwest (Chicago IL specifically) and cannot play due to the high latency. It appears to be an issue with those of us going through Chicago Level3 from looking at everyone's trace routes in this thread. http://us.battle.net/d3/en/forum/topic/17086419492?page=1 I made a new thread as the OP from the other thread is having a different issue I believe. That thread was also started 2 days ago, when this issue started today. I was playing with <100ms latency and then it jumped up and I was rubber banding all over the screen. Tracing route to 12.129.209.26 over a maximum of 30 hops 1 1 ms <1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 8 ms 7 ms 7 ms bvi80.aggr2.chgo.il.rcn.net [207.229.191.131] 4 10 ms 11 ms 15 ms bdle3.border1.eqnx.il.rcn.net [207.172.15.212] 5 66 ms 170 ms 215 ms te-4-2.car3.Chicago1.Level3.net [4.28.58.181] 6 18 ms 11 ms 11 ms 192.205.37.149 7 93 ms 78 ms 76 ms cr1.cgcil.ip.att.net [12.122.133.34] 8 77 ms 79 ms 84 ms cr2.dvmco.ip.att.net [12.122.31.85] 9 76 ms 76 ms 80 ms cr1.slkut.ip.att.net [12.122.30.25] 10 72 ms 65 ms 65 ms cr2.la2ca.ip.att.net [12.122.30.30] 11 65 ms 59 ms 59 ms gar5.lsrca.ip.att.net [12.122.85.33] 12 60 ms 59 ms 59 ms 12.122.251.186 13 80 ms 79 ms 74 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242] 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * #1 4/27/2015 +3 Login to rate Reply Quote MrMoose #1443 Profile MrMoose Posts: 27 View profile Also in the Midwest (Madison, WI), also having the same issue. I can barely even log into the game half the time. This just started today when I got home from work, ready to play some D3 :( Tracing route to 12.129.209.26 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms [192.168.1.1] 2 * * * Request timed out. 3 11 ms 11 ms 12 ms dtr01ftbgwi-tge-0-6-0-3.ftbg.wi.charter.com [96. 34.25.58] 4 13 ms 16 ms 14 ms crr01ftbgwi-bue-4.ftbg.wi.charter.com [96.34.18. 108] 5 19 ms 14 ms 16 ms crr01euclwi-bue-1.eucl.wi.charter.com [96.34.16. 77] 6 19 ms 15 ms 15 ms bbr01euclwi-bue-4.eucl.wi.charter.com [96.34.2.4 ] 7 * 22 ms 21 ms 10-2-15.ear2.Chicago2.Level3.net [4.15.84.21] 8 21 ms 19 ms 23 ms 192.205.37.149 9 86 ms 84 ms 77 ms cr1.cgcil.ip.att.net [12.122.133.34] 10 79 ms 72 ms 72 ms cr2.dvmco.ip.att.net [12.122.31.85] 11 72 ms 75 ms 74 ms cr1.slkut.ip.att.net [12.122.30.25] 12 88 ms 89 ms 96 ms cr2.la2ca.ip.att.net [12.122.30.30] 13 94 ms 90 ms 93 ms gar5.lsrca.ip.att.net [12.122.85.33] 14 74 ms 75 ms 76 ms 12-122-254-230.attens.net [12.122.254.230] 15 295 ms * * 206.16.68.42 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * [Post edited one time, last edit by MrMoose#1443 at April-27-2015 3:56 PM PDT (10 years ago)]

Dankorii	(4/27) North America - Midwest Latency Collection Thread (15)	April-27-2015 5:35 PM PDT (10 years ago)
	Hey folks, I'm sorry to see that some of you are experiencing latency issues. Please post the following information so that we can look for any common factors, and hopefully get this issue escalated for further investigation: -Name of your ISP -City and State you're connecting from -Time of day when you experience the issue (in local time) Let's also 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. You can find the needed IP address in 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. *If the support article linked above lists more than one IP address for the region you play on, please be sure to run a WinMTR to each IP address. * ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback?

Dankorii	(4/27) North America - Midwest Latency Collection Thread (35)	April-28-2015 2:52 PM PDT (10 years ago)
	MrMustang, Posted by: MrMustang04/27/2015 08:36 PM My question is, now that most of the lag seems to be gone, should I run the WinMTR program now or wait til the lag comes back? I'd wait until you experience latency issues again. However, WinMTR can be started whenever you start playing. That way it'll already be running, and if anything happens while you're playing, it should show up in the report. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback?

Dankorii	(4/27) North America - Midwest Latency Collection Thread (36)	April-28-2015 3:04 PM PDT (10 years ago)
	Tarquinn2049 \|------------------------------------------------------------------------------------------\| \| WinMTR statistics \| \| Host - % \| Sent \| Recv \| Best \| Avrg \| Wrst \| Last \| \|------------------------------------------------\|------\|------\|------\|------\|------\|------\| \| 192.168.1.1 - 0 \| 1240 \| 1240 \| 0 \| 1 \| 62 \| 1 \| \| 10.145.244.1 - 1 \| 1236 \| 1235 \| 6 \| 21 \| 163 \| 12 \| \| CHCGILDTCI01.bb.telus.com - 11 \| 867 \| 773 \| 46 \| 111 \| 185 \| 139 \| \|ix-2-1-3-0.tcore2.CT8-Chicago.as6453.net - 12 \| 844 \| 744 \| 59 \| 124 \| 205 \| 93 \| \| 64.86.79.42 - 11 \| 868 \| 774 \| 56 \| 123 \| 205 \| 94 \| \| cr1.cgcil.ip.att.net - 13 \| 824 \| 719 \| 0 \| 120 \| 211 \| 94 \| \| 12.123.251.21 - 12 \| 844 \| 744 \| 0 \| 124 \| 224 \| 106 \| You connection is experiencing a data loss percentage of 11% which starts in the connection's third hop. That hop is part of the Telus network, and the following hop is part of Tata Communication's network, which is a peering partner being used by Telus. The issue could be due to congestion between those two networks, or it could be due to something failing in either network. Either way, this is something that you are going to want to contact your ISP about, so that they can look into the issue for you. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback?

Dankorii	(4/27) North America - Midwest Latency Collection Thread (37)	April-28-2015 3:15 PM PDT (10 years ago)
	Jimjonson, \|------------------------------------------------------------------------------------------\| \| WinMTR statistics \| \| Host - % \| Sent \| Recv \| Best \| Avrg \| Wrst \| Last \| \|------------------------------------------------\|------\|------\|------\|------\|------\|------\| \| 10.2.208.1 - 17 \| 345 \| 287 \| 0 \| 10 \| 36 \| 6 \| \| COX-68-12-10-146-static.coxinet.net - 28 \| 277 \| 202 \| 6 \| 10 \| 37 \| 12 \| \| COX-68-12-10-92-static.coxinet.net - 38 \| 229 \| 142 \| 0 \| 11 \| 39 \| 12 \| \| dalsbprj02-ae2.0.rd.dl.cox.net - 90 \| 126 \| 13 \| 0 \| 18 \| 35 \| 18 \| \| xe-7-3-0.edge5.Dallas3.Level3.net - 85 \| 132 \| 20 \| 0 \| 14 \| 34 \| 14 \| \| No response from host - 100 \| 116 \| 0 \| 0 \| 0 \| 0 \| 0 \| \| No response from host - 100 \| 116 \| 0 \| 0 \| 0 \| 0 \| 0 \| \| ATT - 91 \| 125 \| 12 \| 0 \| 16 \| 20 \| 14 \| \| cr1.dlstx.ip.att.net - 89 \| 128 \| 15 \| 0 \| 16 \| 21 \| 18 \| \| 12.123.249.165 - 89 \| 127 \| 14 \| 0 \| 17 \| 39 \| 12 \| There's definitely something going on with your connection. You can see in the WinMTR that even on the connection's first hop, it loses 17% of the data going through it. That data loss then gets worse in every following hop. Data loss starting on the first hop usually indicates an issue within your home network. This could be due to a bad cable, failing modem or router, or if using a wireless connection, something could be interfering with the wireless signal. If you are using a wireless connection, try using a wired one and then run another WinMTR to see if the data loss percentage improves. If the issue persists on a wired connection, try power cycling the connection and flushing the DNS, and then run another WinMTR to see if there is any improvement. If the issue persists, you are going to want to contact your ISP for further assistance. Here's a support article with steps on how to power cycle: Resetting Network Devices If that doesn't help try flushing the DNS. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback?

Name:
Email address:	(optional)
Feedback: