Can't play for 3 days now...

Technical Support
So, I can't play the game whatsoever. It takes 2-3 minutes just to log in, once I'm in I can't do anything. I join a game and I instantly become lagged to death and it takes 5 minutes or so before I can actually leave the game. I start up my own game and the same thing happens. The auction house button is grayed out, which I read will occasionally happen after the maintenance. So what gives? My latency has been horrible the past 3 days and haven't been able to do squat (Normal latency is 125 and lately it's in the yellow and red).

Things I have checked...
Processes: Fine, nothing is out of the ordinary and I do check often.
Internet Connection: Once again this is fine, I get my normal speeds and the browser speed has not changed.
Computer: More than fine quad core, 8 gigs DDR3 RAM, (2) 5770's and raid 0 ssd's. All functioning and monitored.

Am I missing anything here? Is anybody else experiencing this as well? East Coaster here by the way...
RodSRT,

Let's start with taking a traceroute.

https://us.battle.net/support/en/article/performing-a-traceroute
Typing this in and it say's system cannot find the path specified.

tracert 12.129.209.68 > .\Desktop\tracert.txt
RodSRT,

The instructions assume you're in the users folder where the Desktop directory is. I need to get them changed as it's not correct as written.

Do it this way instead.

tracert 12.129.209.68 > C:\tracert.txt

This will create a text file on your C drive that you need to then cut and paste the contents of when the trace is finished in a few mminutes.
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 7 ms 7 ms 3 ms esr9850.esr9850 [192.168.0.1]
2 4 ms 5 ms 14 ms 10.0.0.1
3 32 ms 27 ms 27 ms fl-76-4-96-1.dhcp.embarqhsd.net [76.4.96.1]
4 30 ms 30 ms 28 ms fl-69-68-14-105.dyn.embarqhsd.net [69.68.14.105]
5 27 ms 29 ms 28 ms 173-248-66-236.centurylink.net [173.248.66.236]
6 34 ms 27 ms 29 ms bb-wnpkflxe-jx9-02-ae0.core.centurytel.net [208.110.248.94]
7 33 ms 34 ms 33 ms 208-110-248-193.centurylink.net [208.110.248.193]
8 31 ms 33 ms 32 ms bb-miauflws-jx9-01-ae0.core.centurytel.net [208.110.248.101]
9 33 ms 36 ms 33 ms nap-edge-03.inet.qwest.net [67.129.170.101]
10 32 ms 39 ms 34 ms nap-brdr-01.inet.qwest.net [205.171.19.42]
11 37 ms 38 ms 38 ms 192.205.35.101
12 105 ms 103 ms 111 ms 12.122.155.170
13 108 ms 106 ms 103 ms cr2.ormfl.ip.att.net [12.122.1.45]
14 103 ms 104 ms 103 ms cr1.ormfl.ip.att.net [12.122.5.185]
15 108 ms 104 ms 105 ms cr2.hs1tx.ip.att.net [12.122.1.5]
16 111 ms 109 ms 103 ms cr1.dlstx.ip.att.net [12.122.28.157]
17 103 ms 108 ms 105 ms cr2.dlstx.ip.att.net [12.122.1.210]
18 107 ms 112 ms 110 ms cr2.la2ca.ip.att.net [12.122.28.178]
19 101 ms 104 ms 108 ms gar29.la2ca.ip.att.net [12.122.129.241]
20 146 ms 200 ms 214 ms 12-122-254-238.attens.net [12.122.254.238]
21 103 ms 102 ms 102 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
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.

Trace complete.
Any thoughts?
RodSRT,

Have you changed anything at all in your network setup lately? The trace looks normal. All I really see that's maybe related is you're double natting. That's having two devices assigning IP addresses. Your modem is assigning an address to your router which in turn assigns addresses to your devices. It's just an extra layer of address translation, not especially bad to do but not good either.

Can you try bypassing the router for now and just connect your pc straight to the modem and see if there's a difference? It looks like you're probably using a wireless connection too based on the first hop times so you'll need to use a wired connection instead. Wireless can also be problematic as a lot of things can interfere with the signal.
experiencing the same here.
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.11.1
2 9 ms 9 ms 8 ms 100.65.0.1
3 11 ms 9 ms 10 ms 121.96.7.26
4 9 ms 9 ms 9 ms 121.96.7.26
5 11 ms 11 ms 12 ms 121.96.7.13
6 10 ms 10 ms 13 ms 121.96.1.106
7 10 ms 10 ms 9 ms 202.78.119.1
8 189 ms 217 ms 217 ms hnk-b2-link.telia.net [80.239.132.117]
9 184 ms 182 ms 181 ms las-bb1-link.telia.net [213.155.134.194]
10 185 ms 182 ms * att-ic-149001-las-bb1.c.telia.net [213.248.88.30]
11 180 ms 178 ms 188 ms cr1.la2ca.ip.att.net [12.123.30.6]
12 177 ms 188 ms 185 ms gar20.la2ca.ip.att.net [12.122.128.181]
13 185 ms 175 ms 242 ms 12-122-254-234.attens.net [12.122.254.234]
14 173 ms 169 ms 170 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.

Trace complete.
Same here from Germany

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 * * * Request timed out.
2 11 ms 15 ms 10 ms 172.30.22.65
3 27 ms 11 ms 17 ms 172.30.30.65
4 44 ms 112 ms 107 ms po1.franco15.fra.seabone.net [89.221.34.16]
5 104 ms 101 ms 101 ms 192.205.36.229
6 179 ms 229 ms 226 ms cr1.n54ny.ip.att.net [12.122.86.6]
7 * 183 ms 182 ms cr2.cgcil.ip.att.net [12.122.1.2]
8 174 ms 175 ms 273 ms cr1.cgcil.ip.att.net [12.122.2.53]
9 178 ms 179 ms 231 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 180 ms * 179 ms cr1.slkut.ip.att.net [12.122.30.25]
11 182 ms 182 ms 181 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 189 ms 249 ms 173 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 177 ms 176 ms 177 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.122.254.234]
14 179 ms 246 ms 181 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.12
9.193.254]
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.

Trace complete.
Same for me, but it started when I tried to play the new patch. My latency goes over 1000ms sometimes.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 1 ms 2 ms 1 ms 192.168.0.1
2 35 ms 22 ms 20 ms blk-222-132-1.eastlink.ca [24.222.132.1]
3 12 ms 15 ms 10 ms ns-nwgl-asr002.eastlink.ca [24.222.226.149]
4 18 ms 19 ms 21 ms ns-hlfx-dr002.ns.eastlink.ca [24.215.102.149]
5 18 ms 18 ms 19 ms ns-hlfx-br002.ns.eastlink.ca [24.215.102.221]
6 44 ms 61 ms 40 ms xe-0-3-0.mtl10.ip4.tinet.net [77.67.70.77]
7 60 ms 62 ms 57 ms xe-7-0-0.nyc20.ip4.tinet.net [89.149.187.53]
8 44 ms 44 ms 43 ms 192.205.37.37
9 114 ms 114 ms 113 ms cr1.n54ny.ip.att.net [12.122.86.6]
10 115 ms 112 ms 115 ms cr2.cgcil.ip.att.net [12.122.1.2]
11 117 ms 111 ms 114 ms cr1.cgcil.ip.att.net [12.122.2.53]
12 114 ms 113 ms 114 ms cr2.dvmco.ip.att.net [12.122.31.85]
13 113 ms 115 ms 112 ms cr1.slkut.ip.att.net [12.122.30.25]
14 112 ms 111 ms 112 ms cr2.la2ca.ip.att.net [12.122.30.30]
15 107 ms 111 ms 110 ms gar29.la2ca.ip.att.net [12.122.129.241]
16 110 ms 113 ms 110 ms 12-122-254-238.attens.net [12.122.254.238]
17 108 ms 112 ms 109 ms ns1326.ztomy.com [206.16.68.46]
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.

Trace complete.

Join the Conversation

Return to Forum