 | Latency isolated to Diablo 3 (w/ Pathping)(1) | Category: Technical SupportApril-2-2014 6:55 PM PDT (9 years ago)  |
| I have serious latency issues while playing D3. It seems to get worse to borderline unplayable during battles (could be environments are completely local and it happens constantly). I go from green (50-100ms) to yellow or red (300-1200) and die constantly. I never had this issue before RoS. Please advise. I've used a latency monitor while playing and my connection is healthy. I've run a pathping test for technical purposes. The problems begin with Battle.net servers. --------------------------------------------------------------------------------- Tracing route to 12.129.209.68 over a maximum of 30 hops 0 dax-win.hsd1.mn.comcast.net. [10.0.1.3] 1 10.0.1.1 2 96.117.72.1 3 te-0-5-0-6-sur01.nmpls.mn.minn.comcast.net [68.85.167.165] 4 te-0-7-0-2-ar01.roseville.mn.minn.comcast.net [69.139.219.54] 5 he-1-11-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.94.73] 6 pos-1-4-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.162] 7 192.205.37.21 8 cr1.cgcil.ip.att.net [12.122.133.106] 9 cr2.dvmco.ip.att.net [12.122.31.85] 10 cr1.slkut.ip.att.net [12.122.30.25] 11 cr2.la2ca.ip.att.net [12.122.30.30] 12 gar20.la2ca.ip.att.net [12.122.128.181] 13 12-122-254-234.attens.net [12.122.254.234] 14 mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254] 15 12.129.209.68 Computing statistics for 375 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 dax-win.hsd1.mn.comcast.net. [10.0.1.3] 0/ 100 = 0% | 1 70ms 1/ 100 = 1% 1/ 100 = 1% 10.0.1.1 0/ 100 = 0% | 2 190ms 1/ 100 = 1% 1/ 100 = 1% 96.117.72.1 0/ 100 = 0% | 3 179ms 0/ 100 = 0% 0/ 100 = 0% te-0-5-0-6-sur01.nmpls.mn.minn.comcast.net [68.85.167.165] 0/ 100 = 0% | 4 206ms 1/ 100 = 1% 1/ 100 = 1% te-0-7-0-2-ar01.roseville.mn.minn.comcast.net [69.139.219.54] 0/ 100 = 0% | 5 244ms 1/ 100 = 1% 1/ 100 = 1% he-1-11-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.94.73] 0/ 100 = 0% | 6 263ms 1/ 100 = 1% 1/ 100 = 1% pos-1-4-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.162] 0/ 100 = 0% | 7 302ms 1/ 100 = 1% 1/ 100 = 1% 192.205.37.21 0/ 100 = 0% | 8 --- 100/ 100 =100% 100/ 100 =100% cr1.cgcil.ip.att.net [12.122.133.106] 0/ 100 = 0% | 9 --- 100/ 100 =100% 100/ 100 =100% cr2.dvmco.ip.att.net [12.122.31.85] 0/ 100 = 0% | 10 --- 100/ 100 =100% 100/ 100 =100% cr1.slkut.ip.att.net [12.122.30.25] 0/ 100 = 0% | 11 --- 100/ 100 =100% 100/ 100 =100% cr2.la2ca.ip.att.net [12.122.30.30] 0/ 100 = 0% | 12 --- 100/ 100 =100% 100/ 100 =100% gar20.la2ca.ip.att.net [12.122.128.181] 0/ 100 = 0% | 13 --- 100/ 100 =100% 100/ 100 =100% 12-122-254-234.attens.net [12.122.254.234] 0/ 100 = 0% | 14 --- 100/ 100 =100% 100/ 100 =100% mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254] 0/ 100 = 0% | 15 320ms 0/ 100 = 0% 0/ 100 = 0% 12.129.209.68 Trace complete. | ||
 | Latency isolated to Diablo 3 (w/ Pathping)(2) | April-2-2014 7:29 PM PDT (9 years ago) |
| eighteesix, Computing statistics for 375 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 dax-win.hsd1.mn.comcast.net. [10.0.1.3] 0/ 100 = 0% | 1 70ms 1/ 100 = 1% 1/ 100 = 1% 10.0.1.1 0/ 100 = 0% | 2 190ms 1/ 100 = 1% 1/ 100 = 1% 96.117.72.1 0/ 100 = 0% | 3 179ms 0/ 100 = 0% 0/ 100 = 0% te-0-5-0-6-sur01.nmpls.mn.minn.comcast.net [68.85.167.165] 0/ 100 = 0% | 4 206ms 1/ 100 = 1% 1/ 100 = 1% te-0-7-0-2-ar01.roseville.mn.minn.comcast.net [69.139.219.54] 0/ 100 = 0% | 5 244ms 1/ 100 = 1% 1/ 100 = 1% he-1-11-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.94.73] 0/ 100 = 0% | 6 263ms 1/ 100 = 1% 1/ 100 = 1% pos-1-4-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.162] Your pathping actually shows a 1% data loss that starts on hop 1, and continues in every hop after that. This is most likely going to be related to the same issue that I mentioned in the other thread, but since it starts on hop 1, it could be your modem or router causing it. I would first try a a power cycle and if that doesn't help, contact Comcast. Here's a support article with steps on how to do that: Resetting Network Devices If that doesn't work try flushing the DNS. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency isolated to Diablo 3 (w/ Pathping)(18) | April-3-2014 1:54 PM PDT (9 years ago) |
| eighteesix, The issue that Californian Comcast users were experiencing yesterday should be resolved now. However; I checked and it looks like Comcast may still be having some issues in other parts of the country. Comcast outage map Also, can you post some network information? * Windows Xp, Vista, 7,or 8 (also include if it's a 32 or 64 bit version) * Firewall (McAfee, Norton, ZoneAlarm, etc.) * Network Adapter brand, model, driver date, and driver version number (Steps below) 1. Click Start. 2. Click Control Panel. 3. Double-click on the System icon (in Windows XP, you may need to click Switch to Classic 4. View on the left hand side of the screen). 5. Select the Hardware tab. 6. Click on Device Manager 7. Expand the section labeled Network Adapters. 8. Right-click on your network card and select Properties. 9. Click on the "Driver" tab at the top * Router brand and model # (this should be printed somewhere on the front or back or bottom) * Cable or DSL Modem brand and model #(this should be printed somewhere on the front or back or bottom) * Is the connection wired or wireless * Location (City, State) ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Latency isolated to Diablo 3 (w/ Pathping)(20) | April-3-2014 7:52 PM PDT (9 years ago) |
| eighteesix, Thanks for the update. Let me know what happens after you get a chance to test in-game. ______________________________________________________ I'm available Monday through Friday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
