Good Afternoon, my wife and I have developed an ongoing issue with Instance Transfer Aborted since the launch of BFA. I have deleted and reinstalled World of Warcraft in it's entirety on my PC, tried without utilizing addons on the fresh install, and it appears to have had no affect. Wired or Wireless does not have any impact either. I am seeking alternative ideas to game files, addons, and WiFi as I have eliminated all 3 from being the issue.
My internet connection as tested by speedtest.net returns the following:
PING: 12ms DOWNLOAD: 72.66Mbps UPLOAD 18.49Mbps
Sourceforge.net/speedtest returns:
PING: 21ms DOWNLOAD: 72.1Mbps UPLOAD: 23.2Mbps JITTER: 7ms BUFFERBLOAT: 49ms down, 19ms up PACKET LOSS: 0%
I'm at a loss! thanks all
Hello Vysthril!
Sorry to hear you're having connection issues changing zones... speed tests are intended to measure your maximum potential bandwidth, so to do that they will calibrate and test speeds to the nearest destination available. They won't tell us much about the specific path your data's traveling to reach the game server, though.
For that, let's run a WinMTR test. This robust test will show us how your data is traveling, and if there are any issues at the 'checkpoints' along the way.
Running WinMTR
The results of the test can be included in a reply to the forum post. Highlight the text then click the </> button in the editor for formatting.
Sorry to hear you're having connection issues changing zones... speed tests are intended to measure your maximum potential bandwidth, so to do that they will calibrate and test speeds to the nearest destination available. They won't tell us much about the specific path your data's traveling to reach the game server, though.
For that, let's run a WinMTR test. This robust test will show us how your data is traveling, and if there are any issues at the 'checkpoints' along the way.
Running WinMTR
The results of the test can be included in a reply to the forum post. Highlight the text then click the </> button in the editor for formatting.
Thank you for the quick response. Here is a paste of about 15-20 min worth of running.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 1392 | 1392 | 0 | 1 | 76 | 1 |
| 192.168.2.1 - 0 | 1392 | 1392 | 1 | 1 | 162 | 3 |
|lo0-100.BLTMMD-VFTTP-307.verizon-gni.net - 3 | 1250 | 1214 | 4 | 7 | 239 | 6 |
| B3307.BLTMMD-LCR-22.verizon-gni.net - 3 | 1282 | 1254 | 4 | 9 | 267 | 10 |
| No response from host - 100 | 278 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 278 | 0 | 0 | 0 | 0 | 0 |
| 0.et-7-3-0.BR1.IAD8.ALTER.NET - 3 | 1270 | 1240 | 6 | 10 | 245 | 11 |
| lag-78.ear2.WashingtonDC12.Level3.net - 100 | 280 | 2 | 0 | 10 | 11 | 10 |
| No response from host - 100 | 278 | 0 | 0 | 0 | 0 | 0 |
| BLIZZARD-EN.ear3.Washington1.Level3.net - 3 | 1290 | 1264 | 9 | 12 | 150 | 11 |
| ae1-br01-eqdc2.as57976.net - 3 | 1250 | 1214 | 26 | 32 | 255 | 30 |
| et-0-0-2-br01-eqch2.as57976.net - 3 | 1271 | 1242 | 26 | 39 | 4348 | 28 |
| be1-pe02-eqch2.as57976.net - 3 | 1254 | 1219 | 25 | 29 | 225 | 27 |
| 24.105.62.129 - 3 | 1254 | 1219 | 27 | 32 | 274 | 31 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I did not experience any instance transfers that aborted - while I tried to cause one. I'll reset it occasionally and try to see if I can capture next time one happens.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 1392 | 1392 | 0 | 1 | 76 | 1 |
| 192.168.2.1 - 0 | 1392 | 1392 | 1 | 1 | 162 | 3 |
|lo0-100.BLTMMD-VFTTP-307.verizon-gni.net - 3 | 1250 | 1214 | 4 | 7 | 239 | 6 |
| B3307.BLTMMD-LCR-22.verizon-gni.net - 3 | 1282 | 1254 | 4 | 9 | 267 | 10 |
| No response from host - 100 | 278 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 278 | 0 | 0 | 0 | 0 | 0 |
| 0.et-7-3-0.BR1.IAD8.ALTER.NET - 3 | 1270 | 1240 | 6 | 10 | 245 | 11 |
| lag-78.ear2.WashingtonDC12.Level3.net - 100 | 280 | 2 | 0 | 10 | 11 | 10 |
| No response from host - 100 | 278 | 0 | 0 | 0 | 0 | 0 |
| BLIZZARD-EN.ear3.Washington1.Level3.net - 3 | 1290 | 1264 | 9 | 12 | 150 | 11 |
| ae1-br01-eqdc2.as57976.net - 3 | 1250 | 1214 | 26 | 32 | 255 | 30 |
| et-0-0-2-br01-eqch2.as57976.net - 3 | 1271 | 1242 | 26 | 39 | 4348 | 28 |
| be1-pe02-eqch2.as57976.net - 3 | 1254 | 1219 | 25 | 29 | 225 | 27 |
| 24.105.62.129 - 3 | 1254 | 1219 | 27 | 32 | 274 | 31 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I did not experience any instance transfers that aborted - while I tried to cause one. I'll reset it occasionally and try to see if I can capture next time one happens.
Im having this problem too and it seems a lot of people are, a real response from blizzard would be nice. its not my internet it just started Monday.
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 1392 | 1392 | 0 | 1 | 76 | 1 |
| 192.168.2.1 - 0 | 1392 | 1392 | 1 | 1 | 162 | 3 |
|lo0-100.BLTMMD-VFTTP-307.verizon-gni.net - 3 | 1250 | 1214 | 4 | 7 | 239 | 6 |
Vysthril,
This bolded portion shows packet loss which appears to happen right after your local network. It persists through the test and It could be your modem, but it also could be the ISP. I'd reset your modem/router first and foremost. If that doesn't work, hit up your ISP with this test and let them know where this data loss is happening. They should be able to send someone to check it out, or may just need to swap your modem with a new one.
Not to necro my old post but I wanted to give positive feedback for the help now that it appears resolved.
Ultimately this was the result of an outdated Fiber Endpoint (Verizon calls it the ONT). They have now replaced the fiber endpoint and modem, and the issue has appeared to be resolved for over a week straight.
@Drakuloth - thank you again! I really appreciate the help.
Ultimately this was the result of an outdated Fiber Endpoint (Verizon calls it the ONT). They have now replaced the fiber endpoint and modem, and the issue has appeared to be resolved for over a week straight.
@Drakuloth - thank you again! I really appreciate the help.