 | Need help reporting lag problem w/ ISP(1) | Category: Technical SupportMarch-9-2015 10:21 AM PDT (10 years ago)  |
| Not sure what or where exactly is the problem, but I am having major lag spikes in 4-man team or solo Grifts. Got this from: http://us-looking-glass.battle.net Hoping someone can help resolve this with either Battle.net or my ISP. traceroute to 49.144.131.186 (49.144.131.186), 15 hops max, 60 byte packets
| ||
 | Need help reporting lag problem w/ ISP(2) | March-9-2015 6:10 PM PDT (10 years ago) |
| Disciple, Let's 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? | ||
| Need help reporting lag problem w/ ISP(4) | March-9-2015 8:05 PM PDT (10 years ago) |
| Cuber, I already responded to you in another thread about the same issue. Please don't post multiple times about the same issue. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Need help reporting lag problem w/ ISP(11) | March-11-2015 3:13 PM PDT (10 years ago) |
| Disciple, |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | P-2612HWU - 3 | 192 | 188 | 0 | 2 | 20 | 1 | | 124.107.159.254.pldt.net - 2 | 196 | 193 | 24 | 30 | 89 | 37 | | 122.2.135.61.pldt.net - 5 | 176 | 168 | 25 | 31 | 64 | 34 | | 210.213.133.74.static.pldt.net - 2 | 196 | 193 | 26 | 34 | 178 | 36 | | 122.2.175.26.static.pldt.net - 3 | 188 | 183 | 25 | 36 | 128 | 38 | | 210.213.130.166.static.pldt.net - 2 | 196 | 193 | 25 | 32 | 146 | 38 | | 203.131.248.213 - 3 | 192 | 188 | 50 | 56 | 88 | 60 | | ae-1.r23.tkokhk01.hk.bb.gin.ntt.net - 40 | 81 | 49 | 0 | 60 | 106 | 61 | | ae-2.r24.tokyjp05.jp.bb.gin.ntt.net - 6 | 168 | 158 | 93 | 101 | 171 | 104 | | ae-1.r20.tokyjp05.jp.bb.gin.ntt.net - 4 | 183 | 176 | 93 | 101 | 136 | 102 | | ae-2.r20.sttlwa01.us.bb.gin.ntt.net - 15 | 134 | 115 | 184 | 199 | 265 | 194 | | ae-1.r04.sttlwa01.us.bb.gin.ntt.net - 3 | 192 | 188 | 184 | 192 | 225 | 196 | | 192.205.34.117 - 94 | 44 | 3 | 0 | 237 | 258 | 258 | | cr82.st0wa.ip.att.net - 4 | 180 | 173 | 204 | 229 | 264 | 221 | | cr2.ptdor.ip.att.net - 8 | 160 | 148 | 212 | 228 | 268 | 212 | | cr1.ptdor.ip.att.net - 3 | 192 | 187 | 209 | 228 | 265 | 230 | | cr1.sffca.ip.att.net - 6 | 172 | 163 | 206 | 230 | 400 | 224 | | cr1.la2ca.ip.att.net - 7 | 164 | 153 | 211 | 227 | 318 | 229 | | cr2.la2ca.ip.att.net - 4 | 185 | 179 | 212 | 227 | 261 | 214 | | 12.123.249.73 - 4 | 184 | 178 | 206 | 226 | 268 | 220 | The first WinMTR that you posted looked like the connection was losing data packets starting at the very first hop. That can sometimes indicate an issue within your home network. When seeing something like that, it's always a good idea to power cycle the connection and the run another MTR to see if those early issues clear up. |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | P-2612HWU - 0 | 369 | 369 | 0 | 4 | 32 | 4 | | 124.107.159.254.pldt.net - 0 | 369 | 369 | 24 | 30 | 54 | 26 | | 122.2.135.61.pldt.net - 0 | 369 | 369 | 25 | 32 | 58 | 35 | | 210.213.133.74.static.pldt.net - 0 | 369 | 369 | 26 | 36 | 108 | 38 | | 122.2.175.26.static.pldt.net - 0 | 369 | 369 | 26 | 31 | 84 | 26 | | 210.213.130.166.static.pldt.net - 0 | 369 | 369 | 25 | 34 | 150 | 39 | | 203.131.248.213 - 0 | 369 | 369 | 51 | 56 | 83 | 53 | | ae-1.r23.tkokhk01.hk.bb.gin.ntt.net - 33 | 163 | 110 | 51 | 58 | 102 | 52 | | ae-2.r25.tokyjp05.jp.bb.gin.ntt.net - 3 | 334 | 325 | 93 | 99 | 132 | 106 | | ae-2.r20.tokyjp05.jp.bb.gin.ntt.net - 0 | 369 | 369 | 94 | 107 | 182 | 105 | | ae-2.r20.sttlwa01.us.bb.gin.ntt.net - 16 | 233 | 198 | 186 | 192 | 215 | 198 | | ae-1.r04.sttlwa01.us.bb.gin.ntt.net - 0 | 369 | 369 | 186 | 196 | 220 | 197 | | 192.205.34.117 - 99 | 76 | 1 | 0 | 411 | 411 | 411 | | cr82.st0wa.ip.att.net - 0 | 369 | 369 | 348 | 413 | 513 | 373 | | cr2.ptdor.ip.att.net - 0 | 369 | 369 | 341 | 408 | 522 | 358 | | cr2.sffca.ip.att.net - 0 | 369 | 369 | 347 | 412 | 509 | 372 | | cr2.la2ca.ip.att.net - 0 | 369 | 369 | 343 | 414 | 514 | 363 | | 12.123.249.73 - 0 | 369 | 369 | 331 | 408 | 514 | 360 | The early data loss that was seen in the previous WinMTR report seems to have cleared up by the time the second MTR was ran. However, both of the MTRs do have something in common, the data loss seems to increase when it reaches the "ae-1.r23.tkokhk01.hk.bb.gin.ntt.net" hop. That hop is not part of your ISP's local network, and it's outside of our network as well. It's actually part of a peering partner's network which is being used by your ISP to get to our backbone provider. The data loss could be due to too much traffic going through that particular hop, or it could be due to a server not working as intended. Either way, this is something that you are going to want to contact your ISP to have them look into this further, and possibly escalate the issue to their peering partner for further investigation from their end. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Need help reporting lag problem w/ ISP(13) | March-12-2015 7:49 PM PDT (10 years ago) |
| Disciple, Posted by Dankorii | 192.205.34.117 - 99 | 76 | 1 | 0 | 411 | 411 | 411 | How about this bad one, is this already part of your network? That's a router where the ae-1.r04.sttlwa01.us.bb.gin.ntt.net hands off the our AT&T backbone, but the issue isn't starting there. It's starting when the connection is handed off from your ISP to the ae-1.r23.tkokhk01.hk.bb.gin.ntt.net server. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
