Ever since the Oceanic servers downtime a few days ago, I’ve been getting “Transfer Aborted: Instance not found” errors constantly. Can happen when I take any portal, zoning into a N’zoth assault, going into arenas/dungeons, anything.
Playing from HK.
same here, in HK too
Same, HK too. Makes you wonder.
Same problem as well, please fix it blizzard
Having the same problem and playing in HK as well.
I’m playing from Guam on Dreadmaul and this happens about 50% of the times I would be zoning, happens quite often when phasing into new locations,IE taking a flight path from great seal to voldun. It’s happened twice now since I left Ashran on a FP to axefall.
We’ve seen some similar issues with Singapore and Hawaii connections. I renamed the title to help track this issue for Hong Kong connections specifically. I’d assume that the issue may be similar to the other two issues and what I assume may be some filtering/configuration issues on the telia network.
For those experiencing the issue, could you provide a WinMTR test? Run the test until the problem occurs for 10 to 15 minutes. Copy and paste the text file created and paste it between two ~~~ like so:
~~~
WinMTR Here
~~~
If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)
Realm: Caelestrasz
ISP: GTA Teleguam
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 172.20.10.1 - 1 | 973 | 971 | 1 | 3 | 243 | 1 |
| 172.23.232.94 - 1 | 954 | 946 | 22 | 146 | 461 | 202 |
| 10.36.16.9 - 4 | 874 | 847 | 15 | 36 | 429 | 22 |
| 192.168.30.178 - 2 | 930 | 917 | 16 | 39 | 291 | 48 |
| 192.168.30.37 - 1 | 965 | 961 | 17 | 37 | 469 | 24 |
| No response from host - 100 | 197 | 0 | 0 | 0 | 0 | 0 |
| unknown.telstraglobal.net - 1 | 950 | 942 | 168 | 190 | 526 | 190 |
|i-0-6-0-4.hkhh-core02.bi.telstraglobal.net - 1 | 958 | 952 | 169 | 192 | 517 | 192 |
| 202.84.138.46 - 2 | 934 | 922 | 222 | 243 | 525 | 238 |
| i-90.sydp10.telstraglobal.net - 1 | 962 | 957 | 221 | 242 | 491 | 236 |
| unknown.telstraglobal.net - 0 | 980 | 980 | 223 | 249 | 541 | 256 |
| et-0-0-49-br01-eqsy4.as57976.net - 3 | 883 | 862 | 223 | 368 | 4494 | 266 |
| et-0-0-0-pe01-eqsy4.as57976.net - 1 | 977 | 976 | 368 | 394 | 860 | 397 |
| 137.221.66.145 - 1 | 973 | 971 | 319 | 341 | 561 | 334 |
| 103.4.115.248 - 3 | 902 | 882 | 321 | 343 | 556 | 336 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I WinMTR’d to 103.4.115.248, the listed IP for Oceanic servers… the results seem… odd. I started it up, used the portal from garrison to Warspear and instantly got the error 5 times in a row. Played for another 5 minutes before stopping. WinMTR looks like this:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 181 | 181 | 0 | 0 | 12 | 0 |
| 42-3-94-253.static.netvigator.com - 0 | 181 | 181 | 1 | 2 | 11 | 1 |
| 10.193.233.22 - 2 | 169 | 166 | 1 | 2 | 12 | 2 |
| wtsc3a046.netvigator.com - 0 | 181 | 181 | 1 | 2 | 8 | 2 |
| ten0-3-0-0.br04.hkg05.pccwbtn.net - 0 | 181 | 181 | 1 | 2 | 8 | 3 |
| reach.ge9-9.br01.hkg05.pccwbtn.net - 0 | 181 | 181 | 2 | 3 | 66 | 3 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I’ve tested WinMTR’ing to the US West and Central IPs, I actually get more nodes along the path. Is the listed IP for Oceanic wrong?
Here is the pastebin link
dTRiaqyP
Just a quick bump as I’m still experiencing this issue constantly and don’t seem to be getting any notice. Have already lost tons of arena rating not being able to zone in.
Thanks for the connection tests, everyone! It looks like the latency starts spiking at the PCC peering networks, but it’s hard to say that’s what causing the transfer aborted message. There doesn’t seem to be any consistent loss on these tests, but some of these were ran for only 2-3 minutes or less, which doesn’t provide the most accurate reading. Does the same problem happen on an alternative connection?
@Torvix, this one might be a bit different from the HK issues, but the test here is helpful.
The home network here is showing a very high worst latency at 243ms, and a 1% packet loss, throughout the test the high latency remains and there’s consistent 1-3% packet loss. In this situation, it may help to try resetting the network device and if wireless, to try a wired connection. Since the packet loss and high latency start at the home network, you’ll want to contact the ISP to check out what’s going on if any signal/lines might be experiencing issues or if there may be filtering/configuration throughout the connection routing causing the packet loss and latency spikes.
For everyone else, we’ll want a longer test here to see what’s going on with the connection. Could new tests be ran for 10-15 minutes?
Here you go.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 2249 | 2249 | 0 | 0 | 4 | 0 |
| 42-3-94-253.static.netvigator.com - 0 | 2249 | 2249 | 0 | 1 | 12 | 2 |
| 10.193.233.22 - 2 | 2103 | 2066 | 0 | 2 | 22 | 2 |
| wtsc3a046.netvigator.com - 0 | 2248 | 2248 | 1 | 2 | 59 | 2 |
| ten0-3-0-0.br04.hkg05.pccwbtn.net - 0 | 2248 | 2248 | 1 | 2 | 7 | 3 |
| reach.ge9-9.br01.hkg05.pccwbtn.net - 0 | 2248 | 2248 | 2 | 3 | 81 | 2 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 451 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Same thing happening here. In Canada. Every few times I attempt to zone am stuck at loading screen. Have to completely close game/reopen. This isn’t my personal connection.
This has been going on for at least a week now.
Its been 2 weeks since I submitted my ticket about this issue and it is still not fixed!!! Happens every time when I click or zone in an instance and sometimes I DIE while on a flight path!!
Having the same issues - not sure what the cause is, but only been happening in the last 2 or so weeks? Never had this issue since 2004+ of playing WoW on and off across different ISPs, locations, connections across HK.
I’ll be glad when this beta is over, only been going for about a year now.
Another stupid side effect of this issue is not being able to do our daily visions in Vale or Uldum. Once we get the ‘transfer aborted:instance not found’, cannot zone into the instance until ‘next day’.
It’s been 4 days of just transfer aborted errors and not being able to do visions at all to farm my essences / mementos etc. Can devs at least look at a workaround to initiate the trigger for this daily (to enter visions) to a proper zone in instead of just a attempt at zone in?
Agreed, at least we can keep the quests till next day…
Tuesdays are RIP tho
I can’t speak for every other OCE user, but I know playing from Guam my latency is almost always 200-250 ish and I’ve gotten used to that, but like others have said this is nothing to do with our side of the connection, I’ve played for years on the same connection then all of a sudden, 2 maybe 3 weeks ago I start getting this error, I chalked it up to an issue with the mergers going on, then I had found out they weren’t happening yet so I come here to try and find an answer, and it feels like a cut and paste answer “reset your connections it’s high latency on your home connection”. I feel most of us that play, when we do run into a small issue we do the simple checks before wasting our time on the forums. The issue itself would be less annoying if it didn’t cause deaths on flight paths, failures to daily instances, or lost time on keys.