This sounds like the thread would be better off in tech support.
Edit nevermind as I made this post it was moved
This sounds like the thread would be better off in tech support.
Edit nevermind as I made this post it was moved
I have been able to log in without much problems, but since yesterday I’ve been getting “Transfer Abort: Instance not available” whenever I either move from Zone to Zone, or try to go into a Dungeon/Instance.
I’ll usually be able to get in after multiple attempts but it’s very annoying.
I’m also playing from Singapore, using Singtel, WRA server.
4 posts were merged into an existing topic: [Main Thread] Hawaiian Telcom - Transfer Aborted: Instance Not Found
I was having the same issues this morning, so I installed a VPN service, and the transfer aborts seem to have stopped. No idea what that means.
I’ve been getting this issue since about 48 hours ago.
It takes multiple failed loading screens to get into an instance or through a portal. And when inside a dungeon/instance, if I get another “Transfer Aborted: Instance not Found”, i get booted out to the character select screen, and have to wait for the “Not your Instance” mechanic to teleport me out and if that fails, I get booted to the character select screen again.
I am unable to take Flight Paths because if I do, and when the FP crosses from one zone to the next, I might get a “Transfer Aborted: Instance Not Found” which immediately boots me off the FP in mid air to my death.
I’ve lost the daily Vision quest because of it.
I’ve done literally everything I could find suggested, from Flushing my DNS, to resetting my router, to removing the WTF and local interface files, to scan and repair, to uninstalling and reinstalling.
I’ve already checked my network repeatedly seems like there’s nothing wrong on my home network, and I’ve seen several posts of issues similar to mine with no fixes in sight.
What gives?
Hey there Dauvit,
This specific error – “Transfer Aborted: Instance Not Found” – indicates that something prevented you from establishing a stable connection to the game server. This can be caused by a variety of things from corrupted local game files to a network-related problem. With that in mind, considering the troubleshooting steps you’ve already tried we’ll want to have you run a WinMTR network test while the error occurs in-game so that we can further investigate the problem. Here are the instructions:
WinMTR goes here
If you have issues pasting here, please use Pastebin and post the link (ex: Pastebin (dot) com/123456).
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.254 - 0 | 965 | 965 | 0 | 0 | 7 | 0 |
| bb115-66-71-254.singnet.com.sg - 0 | 965 | 965 | 1 | 3 | 110 | 2 |
| 202.166.123.130 - 0 | 965 | 965 | 1 | 2 | 23 | 2 |
| 202.166.123.129 - 0 | 965 | 965 | 1 | 1 | 31 | 1 |
| ae8-0.qt-cr03.singnet.com.sg - 0 | 965 | 965 | 1 | 1 | 42 | 2 |
| ae13-0.tp-cr03.singnet.com.sg - 0 | 965 | 965 | 1 | 2 | 37 | 2 |
| ae4-0.tp-er03.singnet.com.sg - 0 | 965 | 965 | 1 | 2 | 36 | 2 |
| 203.208.191.113 - 0 | 965 | 965 | 1 | 2 | 48 | 1 |
| 203.208.182.249 - 0 | 965 | 965 | 2 | 2 | 67 | 2 |
| 203.208.173.106 - 0 | 965 | 965 | 177 | 177 | 200 | 177 |
| 203.208.172.234 - 0 | 965 | 965 | 178 | 179 | 229 | 179 |
| palo-b22-link.telia.net - 0 | 965 | 965 | 239 | 248 | 473 | 240 |
| las-b24-link.telia.net - 1 | 949 | 945 | 240 | 241 | 265 | 241 |
| las-b21-link.telia.net - 0 | 965 | 965 | 242 | 242 | 261 | 242 |
| blizzard-ic-348621-las-b21.c.telia.net - 0 | 965 | 965 | 238 | 243 | 358 | 238 |
| ae1-br01-eqla1.as57976.net - 0 | 961 | 961 | 244 | 387 | 4157 | 245 |
| No response from host - 100 | 193 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-0-pe03-swlv10.as57976.net - 0 | 965 | 965 | 247 | 250 | 374 | 247 |
| 137.221.105.2 - 0 | 965 | 965 | 247 | 247 | 256 | 247 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Hey Dauvit! Thanks for taking the time to run that test. Looking at the data, there’s a significant spike in latency occurring on the 10th “hop” your connection takes on the route to our servers:
203.208.173.106 - 0 | 965 | 965 | 177 | 177 | 200 | 177 |
Since the latency problem affects all subsequent hops leading up to our servers, this test indicates that there is a problem causing instability on that 10th hop.
A quick way to confirm that the issue is isolated to your regular network is by temporarily testing an alternate network, such as a VPN or mobile hotspot.
With that in mind, this would be an issue to bring up to your ISP as they may need to investigate the instability occurring on that hop, or reroute your connection so that it avoids the troublesome hop. Keep in mind that you can request to speak with a “level 2 or level 3 technician” when contacting the ISP, as the front-line representatives typically only have access to basic diagnostics and troubleshooting tools. In addition, I encourage forwarding the WinMTR data to whomever you speak with when contacting the ISP, because if they’re able to interpret the data, this may enable them to diagnose and resolve the issue more quickly.
I hope this helps get things fixed up so you can get back to playing as normal!
im in singapore and im facing the same issue even since this week maintanance. please check
I have this same issue but I am on the west coast. I’ve been having connection issues for several weeks prior to this change and I currently have a ticket open with tech support about it.
Same issue, except im in Singapore. currently communicating with blizzard tac
there is no way it would be ISP problem. my ping and traceroute to google.com seems fine.
It should be the blizzard servers.
Same issues, get lockout for leaving pvp when I couldnt even enter the instance
Adjusted the title here to get more traction on the issue and moved a few threads over to this one. Thank you for your reports! We’re getting tracking for this issue, but we’ll need some information to check on what’s happening with the connection from and to Singapore and our servers.
For those of you experiencing issues, please include the following:
~~~
WinMTR Here
~~~
If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456
)
For those experiencing issues with Hawaii connections, please refer to this thread instead. If you are experiencing similar issues, but neither Singapore or Hawaii is relevant to your issue, please create your own thread.
Dear Sir / Mdm,
I also have same issues, connecting from Singapore to Blackrock server.
I tried Win / Mac environment and got same issues so it would not be caused by local PC.
Same as others, I feel it started from last Wed maintenance.
I saw another thread that users from Hawaii has same issues.
So I would imagine it is not ISP issues.
I am having the same bloody issue. This issue only happened 2-3 days ago when Blizzard and its stealth crew decided to implement stealth changes that kicked everyone off the server.
This problem might be solved if you get someone not from Singapore queueing for a battleground on a US server
I suggest having technicians that know what they are actually doing and actually communicating with the playerbase.
Same issue here. Worse, trying to open an in-game ticket doesn’t go through at all. It’s getting really frustrating trying to play visions when it keeps giving me the daily cooldown after “transfer aborted”.
Realm: Aegwynn US Central
ISP: Singapore Telecommunications Ltd, Magix Services (Singtel)
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.254 - 0 | 373 | 373 | 1 | 4 | 416 | 4 |
| bb219-74-144-254.singnet.com.sg - 0 | 373 | 373 | 2 | 14 | 420 | 43 |
| 202.166.123.134 - 0 | 373 | 373 | 2 | 6 | 418 | 5 |
| 202.166.123.133 - 0 | 373 | 373 | 2 | 5 | 404 | 3 |
| ae8-0.tp-cr03.singnet.com.sg - 0 | 373 | 373 | 2 | 5 | 412 | 3 |
| ae4-0.tp-er03.singnet.com.sg - 0 | 373 | 373 | 2 | 6 | 418 | 17 |
| 203.208.191.113 - 0 | 373 | 373 | 2 | 7 | 423 | 4 |
| 203.208.182.249 - 0 | 373 | 373 | 2 | 6 | 407 | 4 |
| 203.208.152.214 - 0 | 373 | 373 | 173 | 178 | 568 | 174 |
| 203.208.172.234 - 0 | 373 | 373 | 187 | 191 | 605 | 188 |
| palo-b22-link.telia.net - 0 | 373 | 373 | 190 | 196 | 601 | 191 |
| sjo-b21-link.telia.net - 0 | 373 | 373 | 173 | 177 | 577 | 175 |
| las-b21-link.telia.net - 0 | 373 | 373 | 173 | 177 | 585 | 177 |
| blizzard-ic-348621-las-b21.c.telia.net - 0 | 373 | 373 | 174 | 182 | 581 | 175 |
| ae1-br02-eqla1.as57976.net - 0 | 373 | 373 | 235 | 246 | 640 | 236 |
| et-0-0-3-br02-eqch2.as57976.net - 0 | 372 | 372 | 239 | 258 | 1380 | 241 |
| et-0-0-1-pe02-eqch2.as57976.net - 0 | 373 | 373 | 234 | 240 | 628 | 237 |
| chi-eqch2-ia-bons-02.as57976.net - 0 | 373 | 373 | 236 | 239 | 634 | 237 |
| 24.105.62.129 - 0 | 373 | 373 | 234 | 238 | 645 | 236 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Same issue occurring intermittently ever since Wednesday’s hotfix
Thank you, Feylara! I’ve got this test and details added over to our tracking. The connection test looks fine here, but we’re comparing the data with other tests to pinpoint the exact issue.
For those experiencing this issue, please include the requested details mentioned above.
In the mean time, we’ve seen a small amount of reports where a VPN helps alleviate the issue. It’s worth trying if a VPN or alternative connection may help in this situation.
Real for me is Mal’Ganis
ISP is SingNet / SingTel source IP 42.60.138.0/24
I am a network engineer and web application developer that has extensive experience with NGINX.
There are thousands of players affected (noted at least in Hawaii and Singapore and elsewhere). It doesn’t only affect WoW but other Blizzard games as well.
Please escalate the issue and stop endlessly asking players themselves to perform diagnosis for you. Traceroutes does not show the problem.
I suspect several issues:
Highly suspect INTERNAL blizzard server issue especially #3-4.
Please escalate internally to your teams.