The problem: I am trying to play Diablo 3 from Blizzard on my PC. During peak hours (8 pm - Midnight) I experience incredibly choppy, laggy gameplay. I have been in constant contact with Blizzard support and have run the gamut of diagnostics and troubleshooting guides. I have now play with all of my settings set to low and have every port what so ever forwarded. Let me be clear that I have done all the basic troubleshooting steps, disabling firewalls, power cycling modems / routers, etc. During my time working with Blizzard they had me run a number of pathpings and traceroutes to their Diablo server (12.129.209.68). Both the pathpings and the traceroutes always timeout at hop 5 (6 if I have my router plugged in). I understand that routers can get in the way of troubleshooting things so I have done everything both with my router in line and also while connected to my modem directly (I am hardwired in, this is not a wireless connection). After an extensive correspondence with Blizzard they recommend I contact my ISP. I did this, a week ago, and they found problems with my connection. They dispatched a technician to my house and he was actually able to find a physical defect in my connection and repair it. Let me add that my other internet services are unaffected, web pages load just as fast as ever and download speeds are right where they should be. I just concluded a 90 minute phone session with Comcast Support during which I was transferred to 5 different departments only for the last guy to tell me that my best option was to come here to the forums and make a post. So I am here. If there is any extra information I can provide that might help shed light on this issue please let me know. For now I will include an example of the pathpings and traceroute results I've been getting of which I have dozens (they're always the same).
Path Ping
Tracing route to 12.129.209.68 over a maximum of 30 hops
0 dFong-PC [192.168.2.222]
1 router.asus.com [192.168.2.1]
2 c-68-33-57-1.hsd1.md.comcast.net [68.33.57.1]
3 xe-4-0-0-32767-sur01.ebaltimorest.md.bad.comcast.net [68.85.81.161]
4 xe-6-0-3-0-ar04.whitemarsh.md.bad.comcast.net [68.85.114.161]
5 he-3-3-0-0-10-cr01.newyork.ny.ibone.comcast.net [68.86.94.61]
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 dFong-PC [192.168.2.222]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com [192.168.2.1]
2/ 100 = 2% |
2 173ms 4/ 100 = 4% 2/ 100 = 2% c-68-33-57-1.hsd1.md.comcast.net [68.33.57.1]
0/ 100 = 0% |
3 156ms 5/ 100 = 5% 3/ 100 = 3% xe-4-0-0-32767-sur01.ebaltimorest.md.bad.comcast.net [68.85.81.161]
0/ 100 = 0% |
4 172ms 2/ 100 = 2% 0/ 100 = 0% xe-6-0-3-0-ar04.whitemarsh.md.bad.comcast.net [68.85.114.161]
4/ 100 = 4% |
5 115ms 6/ 100 = 6% 0/ 100 = 0% he-3-3-0-0-10-cr01.newyork.ny.ibone.comcast.net [68.86.94.61]
Trace complete.
Traceroute:
Tracing route to 12.129.209.68 over a maximum of 30 hops
1 1 ms <1 ms <1 ms router.asus.com [192.168.2.1]
2 38 ms 26 ms 29 ms c-68-33-57-1.hsd1.md.comcast.net [68.33.57.1]
3 8 ms 10 ms 10 ms xe-4-0-0-32767-sur01.ebaltimorest.md.bad.comcast.net [68.85.81.161]
4 13 ms 10 ms 10 ms xe-6-0-3-0-ar04.whitemarsh.md.bad.comcast.net [68.85.114.161]
5 17 ms 15 ms 19 ms he-3-3-0-0-10-cr01.newyork.ny.ibone.comcast.net [68.86.94.61]
6 * * * Request timed out.
7 18 ms 19 ms 18 ms 192.205.37.33
8 81 ms 82 ms 83 ms cr1.n54ny.ip.att.net [12.122.131.86]
9 83 ms 84 ms 82 ms cr2.cgcil.ip.att.net [12.122.1.2]
10 80 ms 83 ms 82 ms cr1.cgcil.ip.att.net [12.122.2.53]
11 81 ms 100 ms 83 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 84 ms 84 ms 112 ms cr1.slkut.ip.att.net [12.122.30.25]
13 84 ms 82 ms 83 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 79 ms 78 ms 79 ms gar20.la2ca.ip.att.net [12.122.128.181]
15 80 ms 80 ms 80 ms 12.122.251.190
16 81 ms 81 ms 96 ms 206.16.68.46
17 82 ms 81 ms 81 ms 12.129.199.178
18 81 ms 82 ms 94 ms 12.129.209.68
Trace complete.