 | Hey Dankorri - Latency fix please!(1) | Category: Technical SupportMay-26-2014 3:21 PM PDT (9 years ago)  |
| Disconnects and Latency SOLVED - Kind of - Best part about doing 4 tracerts in a row, shows the issue isn't mine, or my ISP's, but after its handed off to AT&T and most interestingly, the 4th one showing a timeout on Blizzard's end of things. Tracing route to 12.129.209.68 over a maximum of 30 hops 1 2 ms 2 ms 2 ms 192.168.1.254 2 52 ms 33 ms 37 ms d204-191-128-1.abhsia.telus.net [204.191.128.1] 3 29 ms 33 ms 30 ms 154.11.212.130 4 72 ms 68 ms 69 ms chcgildtgr00.bb.telus.com [154.11.11.34] 5 75 ms 70 ms 74 ms d1-3-1-0-7.r04.chcgil09.us.bb.gin.ntt.net [128.242.186.181] 6 70 ms 70 ms 68 ms ae-8.r05.chcgil09.us.bb.gin.ntt.net [129.250.4.221] 7 97 ms 98 ms 103 ms 192.205.32.193 8 153 ms 123 ms 119 ms cr1.cgcil.ip.att.net [12.122.133.162] 9 133 ms 119 ms 128 ms cr2.dvmco.ip.att.net [12.122.31.85] 10 318 ms 169 ms 289 ms cr1.slkut.ip.att.net [12.122.30.25] 11 207 ms 168 ms 219 ms cr2.la2ca.ip.att.net [12.122.30.30] 12 125 ms 207 ms 196 ms gar5.lsrca.ip.att.net [12.122.85.33] 13 298 ms 329 ms 291 ms 12-122-254-226.attens.net [12.122.254.226] 14 200 ms 124 ms 139 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242] 15 164 ms 123 ms 130 ms paxonix-placeholder.lax1.attens.net [12.129.248.118] 16 171 ms 128 ms 124 ms 12.129.209.68 Trace complete. Tracing route to 12.129.209.68 over a maximum of 30 hops 1 5 ms 5 ms 5 ms 192.168.1.254 2 34 ms 30 ms 33 ms d204-191-128-1.abhsia.telus.net [204.191.128.1] 3 32 ms 36 ms 32 ms 154.11.212.130 4 69 ms 68 ms 69 ms chcgildtgr00.bb.telus.com [154.11.11.34] 5 71 ms 70 ms 79 ms d1-3-1-0-7.r04.chcgil09.us.bb.gin.ntt.net [128.242.186.181] 6 73 ms 70 ms 75 ms ae-8.r05.chcgil09.us.bb.gin.ntt.net [129.250.4.221] 7 98 ms 93 ms 93 ms 192.205.32.193 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 282 ms 197 ms 122 ms gar5.lsrca.ip.att.net [12.122.85.33] 13 222 ms 228 ms 215 ms 12-122-254-226.attens.net [12.122.254.226] 14 149 ms 175 ms 150 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242] 15 121 ms 128 ms 133 ms paxonix-placeholder.lax1.attens.net [12.129.248.118] 16 132 ms 125 ms 124 ms 12.129.209.68 Trace complete. Tracing route to 12.129.209.68 over a maximum of 30 hops 1 70 ms 4 ms 2 ms 192.168.1.254 2 37 ms 35 ms 32 ms d204-191-128-1.abhsia.telus.net [204.191.128.1] 3 33 ms 32 ms 33 ms 154.11.212.130 4 82 ms 74 ms 69 ms chcgildtgr00.bb.telus.com [154.11.11.34] 5 72 ms 70 ms * d1-3-1-0-7.r04.chcgil09.us.bb.gin.ntt.net [128.242.186.181] 6 70 ms 70 ms 71 ms ae-8.r05.chcgil09.us.bb.gin.ntt.net [129.250.4.221] 7 103 ms 120 ms 95 ms 192.205.32.193 8 124 ms 123 ms 119 ms cr1.cgcil.ip.att.net [12.122.133.162] 9 131 ms 142 ms 126 ms cr2.dvmco.ip.att.net [12.122.31.85] 10 121 ms 124 ms 127 ms cr1.slkut.ip.att.net [12.122.30.25] 11 127 ms 130 ms 128 ms cr2.la2ca.ip.att.net [12.122.30.30] 12 122 ms 116 ms 130 ms gar5.lsrca.ip.att.net [12.122.85.33] 13 129 ms 127 ms 129 ms 12-122-254-226.attens.net [12.122.254.226] 14 137 ms 173 ms * mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242] 15 129 ms 127 ms 123 ms paxonix-placeholder.lax1.attens.net [12.129.248.118] 16 131 ms 130 ms 121 ms 12.129.209.68 Trace complete. Tracing route to 12.129.209.68 over a maximum of 30 hops 1 2 ms 8 ms 2 ms 192.168.1.254 2 31 ms 30 ms 31 ms d204-191-128-1.abhsia.telus.net [204.191.128.1] 3 35 ms 29 ms 41 ms 154.11.212.130 4 73 ms 70 ms 76 ms chcgildtgr00.bb.telus.com [154.11.11.34] 5 73 ms 78 ms 72 ms d1-3-1-0-7.r04.chcgil09.us.bb.gin.ntt.net [128.242.186.181] 6 71 ms 84 ms 73 ms ae-8.r05.chcgil09.us.bb.gin.ntt.net [129.250.4.221] 7 101 ms 97 ms 132 ms 192.205.32.193 8 127 ms 120 ms * cr1.cgcil.ip.att.net [12.122.133.162] 9 129 ms 128 ms 122 ms cr2.dvmco.ip.att.net [12.122.31.85] 10 131 ms 117 ms 119 ms cr1.slkut.ip.att.net [12.122.30.25] 11 128 ms * 131 ms cr2.la2ca.ip.att.net [12.122.30.30] 12 120 ms 125 ms 119 ms gar5.lsrca.ip.att.net [12.122.85.33] 13 156 ms 121 ms 126 ms 12-122-254-226.attens.net [12.122.254.226] 14 127 ms 124 ms 123 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242] 15 124 ms 124 ms 131 ms paxonix-placeholder.lax1.attens.net [12.129.248.118] 16 125 ms * 130 ms 12.129.209.68 Trace complete. | ||
 | Hey Dankorri - Latency fix please!(11) | May-27-2014 5:10 PM PDT (9 years ago) |
| SteveHepburn, Computing statistics for 400 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Steve-PC.telus [192.168.1.64] 5/ 100 = 5% | 1 12ms 8/ 100 = 8% 3/ 100 = 3% 192.168.1.254 0/ 100 = 0% | 2 40ms 5/ 100 = 5% 0/ 100 = 0% d204-191-128-1.abhsia.telus.net [204.191.128.1] 0/ 100 = 0% | 3 38ms 11/ 100 = 11% 6/ 100 = 6% 154.11.212.130 0/ 100 = 0% | 4 84ms 5/ 100 = 5% 0/ 100 = 0% chcgildtgr00.bb.telus.com [154.11.11.34] 2/ 100 = 2% | 5 77ms 7/ 100 = 7% 0/ 100 = 0% d1-3-1-0-7.r04.chcgil09.us.bb.gin.ntt.net [128.242.186.181] 0/ 100 = 0% | 6 82ms 10/ 100 = 10% 3/ 100 = 3% ae-8.r05.chcgil09.us.bb.gin.ntt.net [129.250.4.221] 0/ 100 = 0% | 7 109ms 7/ 100 = 7% 0/ 100 = 0% 192.205.32.193 3/ 100 = 3% | 8 --- 100/ 100 =100% 90/ 100 = 90% cr1.cgcil.ip.att.net [12.122.133.162] 0/ 100 = 0% | 9 --- 100/ 100 =100% 90/ 100 = 90% cr2.dvmco.ip.att.net [12.122.31.85] 0/ 100 = 0% | 10 --- 100/ 100 =100% 90/ 100 = 90% cr1.slkut.ip.att.net [12.122.30.25] 0/ 100 = 0% | 11 --- 100/ 100 =100% 90/ 100 = 90% cr2.la2ca.ip.att.net [12.122.30.30] 0/ 100 = 0% | 12 --- 100/ 100 =100% 90/ 100 = 90% gar5.lsrca.ip.att.net [12.122.85.33] 0/ 100 = 0% | 13 --- 100/ 100 =100% 90/ 100 = 90% 12-122-254-226.attens.net [12.122.254.226] 0/ 100 = 0% | 14 --- 100/ 100 =100% 90/ 100 = 90% mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242] 0/ 100 = 0% | 15 --- 100/ 100 =100% 90/ 100 = 90% paxonix-placeholder.lax1.attens.net [12.129.248.118] 0/ 100 = 0% | 16 136ms 10/ 100 = 10% 0/ 100 = 0% 12.129.209.68 Trace complete. Your pathping is showing that the connection is losing data packets in just about every hop that it hits before it reaches our backbone server. This is starting with the 5% loss seen between hops 0 and 1 which tells us there may be an issue within your home network. As far as troubleshooting goes, everything that MissCheetah mentioned is pretty much where you would want to start, with the addition of checking that your ethernet cables are not loose and that they are not damaged. I know this is not what you want to hear, and seeing other connection issues being posted about on the forums makes it easy to say that your issue is being caused by something on our end, but based on what you're pathping is showing, you need to first address some issues in your home network. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
