For The Love Of God Fix This Problem @Blizzard. 9 Weeks And still we have this Problem
3 Likes
The issue still persists… not that anyone cares (specially blizzard!) but it still is happening. lots of people still have to use VPN to play for the game THEY PAY to play :).
premium scamming happening right in front of you people and none of you can do anything to prevent it 
5 Likes
just so you know, the problem is still here. not that anyone cares but yeah it’s still here
2 Likes
Hallo Can You Do Something?? can You fix this ?!!? We still stuck in loading we’re using vpn to ply this game with 200ms
Same problem here
Still world server down
Good company. Not fixing it after around 3 months with people complaining.
And here I was thinking that pvp devs were non-existent. It seems technical support is the same.
1 Like
Blizzard Is Using AWS for their games and wow is one of them.and Amazon AWS is Blocking us From Its Services They Know about it but they dont want to do anything
1 Like
I mean the AWS restrictions on Iran’s IP goes back to 2019, that being said this problem happened for a period of time in BFA season 4 like less than 9 months ago or something, I personally linked the old thread to this one. how come back then (less than 9 months ago) Blizzard was able to fix the problem but now all of sudden they can’t?
All this brings me to this conclusion that its not matter of “we can’t fix this problem” rather than “we choose not to solve this problem” due to [insert lame reason] here…
Current state of Blizzard, specially in World of Warcraft department on how they treat their customers is baffling and outrageous compared to old Blizzard (10-15 years ago) standards. if this is how they treat their customers, imagine what they do to their poor employees…
1 Like
we’re still experiencing this problem.can you do something about it blizzard heloooo any blue chatter here? @Blizzard @GameMaster
Adding my voice to this as well. Got stuck on Login screen disconnecting, with Launcher disconnecting, and forcing client logout. Fixd that by enabling IPv6 where available.
Experienced random disconnects, especially when zoning ie, Lvl21 chromie time to WoD. Tried to start expansion by talking to the Vanguard NPC. Loading screen comes up, at 0%, doesnt move and quits back to NPC with Instance not found issue.
Havent changed anything on my side. Had a few ranty posts, all the while filing tickets. After ticket no. 4 got a lengthy response from a more technical GM, which, although it contained good advice, did not solve issue, and included prose to excuse Blizzard Support staff, and implying that it must be me, as I got it to logon via IPv6.
Also they said there are no reported problems like this?
Anyway Heres my MTR from their looking glass tool
(note : blizz doesnt allow ‘links’ so the . have been replaced by - where it thinks there is a link)
MTR:
Start: Mon Feb 15 22:46:23 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15/02/2021 22:46:23 UTC
MTR:
Start: Mon Feb 15 22:46:23 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15/02/2021 22:46:23 UTC
MTR:
Start: Mon Feb 15 22:46:23 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15/02/2021 22:46:23 UTC
MTR:
Start: Mon Feb 15 22:46:23 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.4 0.2 0.6 0.0
2.|-- 37.244.25.130 70.0% 10 296.0 295.5 287.5 302.9 7.7
3.|-- Blizzard 0.0% 10 1.0 0.9 0.7 1.1 0.0
4.|-- 137.221.66.38 0.0% 10 0.5 5.3 0.5 48.1 15.0
5.|-- 137.221.77.52 0.0% 10 7.5 7.9 7.5 11.1 1.0
6.|-- 137.221.65.19 0.0% 10 7.5 15.8 7.5 54.8 17.4
7.|-- 137.221.79.34 0.0% 10 67.6 16.7 7.6 67.6 20.2
8.|-- be1028-er16-thlon-isp-sky-com 0.0% 10 348.6 333.5 272.8 352.8 24.5
9.|-- lag2-sr10-encvt-isp-sky-com 0.0% 10 11.8 11.8 11.6 12.1 0.0
10.|-- bcdf93eb-skybroadband-com 0.0% 10 16.5 16.6 15.9 17.0 0.0
15/02/2021 22:46:23 UTC
MTR:
Start: Mon Feb 15 22:46:23 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0
2.|-- 37.244.25.130 80.0% 10 296.1 299.6 296.1 303.1 4.9
3.|-- Blizzard 0.0% 10 0.9 0.9 0.6 1.1 0.0
4.|-- 137.221.66.38 0.0% 10 0.6 5.3 0.5 47.8 14.9
5.|-- 137.221.77.52 0.0% 10 7.5 7.9 7.3 11.0 1.0
6.|-- 137.221.65.19 0.0% 10 7.5 11.0 7.4 41.8 10.8
7.|-- 137.221.79.34 0.0% 10 67.5 16.6 7.5 67.5 20.2
8.|-- be1028-er16-thlon-isp-sky-com 0.0% 10 348.6 329.4 272.9 352.6 26.6
9.|-- lag2-sr10-encvt-isp-sky-com 0.0% 10 11.8 11.7 11.6 12.1 0.0
10.|-- bcdf93eb-skybroadband-com 0.0% 10 16.7 26.7 16.2 116.6 31.6
15/02/2021 22:46:23 UTC
MTR:
Start: Mon Feb 15 22:46:23 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 0.6 0.0
2.|-- 37.244.25.130 70.0% 10 296.4 295.6 287.6 302.7 7.5
3.|-- Blizzard 0.0% 10 0.9 1.0 0.9 1.1 0.0
4.|-- 137.221.66.38 0.0% 10 0.5 5.4 0.4 48.1 15.0
5.|-- 137.221.77.52 0.0% 10 7.5 8.1 7.5 12.2 1.4
6.|-- 137.221.65.19 0.0% 10 7.5 15.8 7.5 54.8 17.4
7.|-- 137.221.79.34 0.0% 10 67.6 16.7 7.5 67.6 20.2
8.|-- be1028-er16-thlon-isp-sky-com 0.0% 10 348.6 333.6 272.9 352.8 24.5
9.|-- lag2-sr10-encvt-isp-sky-com 0.0% 10 11.8 11.8 11.6 12.1 0.0
10.|-- bcdf93eb-skybroadband-com 0.0% 10 16.7 16.6 15.9 17.4 0.0
15/02/2021 22:46:23 UTC
Updating on this. Not going to mention the support agent or GM names, but be aware that I linked this post as being identical to the issue I have, and I had two posts insinuating I was to fault, and these were all different errors not related.
This is a direct quote taken from the last reply from a more technical support agent -
“The fact is that people getting the same kind of error messages, or disconnection immediatly think they are the same issues with same source when it is most of the time not the case.”
While I am sure this post is meant to try and be helpful and no malice is involved, a simple search of the issue relates many many correlating factors that point to a common cause: Blizzard breaking something. Are we to believe that simulationously thousands of users all did different things to their setup that resulted in exactly the same trangression of errors and disconnections?
Isn’t it logical deduction to work out a common cause? Ah yes. It must be us breaking it because never in the history of software development has there been a bug that slips by without devs noticing and remains unseen until later. Or thats what us peons are meant to believe to finance the CEOs at Blizzard buying a new summer house in Bora Bora.
So in essence:
WoW program cannot login idependant of BNet launcher
WoW Program will only login via above when IPv6 is enabled where available
When there is a zone change where the protocol changes to IPv4, there is a Transfer aborted: Instance not found error
Changing to google DNS does not resolve. When trying to load in a charcter that has somehow made it to these zones, a World Server is down error is shown on character selection screen
Loading times are dramatically increased to 5mins approx
Conclusion - the WoW client has no internet access when using IPv4, and relies on BNet to handle resolution. When zone change occurs, this is handled via system code, and when the protocol is IPv4, fails and so disconnects. I dont think google have faulty dns servers, and the most likely issue is a recent patch which has changed the way it handles IPv6 to IPv4 conversions
UPDATE MORE (a Good update!!!)
Sooo.
Much tweaking and puzzling, I got it working, though I’m unsure if its been rectified behind the scenes or not.
Anyway, heres what I did -
(using Mac btw - you should be able to do the same with windows)
Firstly ‘Enable IPv6 where available’ was enabled in WoW settings
Make sure all addons are off.
Without anything running, I set Link-local as the Configure IPv6 in System Prefrences -> Network
As expected, it failed login. I then unchecked ‘Enable IPv6 where available’ and exited WoW.
Then I set Configure IPv6 back to Automatically, and reloaded launcher, then Play
Lo and Behold. All issues seem to be fixed. No World Server is Down. No zone transition error.
My guess is that somehow the internal settings for IPv6 translation were borked somehow, and this forced a reset.
Not a usual error, but I still think an update fudged this.
It is possible they did a black ops fix and didnt tell us. Let me know if anyone else suddenly has it working.
UPDATE (Bad News 
)
Nope. Didnt work. Brief moment of happiness, then errors all returned.
I hate this game.
1 Like
So you’re saying that we can not ply without IPV6 ? Thats The Reason Why VPN solves The problem? Because maybe Vpn runs on IPv6?
Thats my theory. Whatever was changed in the app made some installs of the client incompatible with IPv4, as it seems when crashing occurs in game its when the local and world IP protocols are different, and failure to login is when your character is in that zone, or is transitioning via flightpath. I’m honestly surprised this hasn’t been picked up or mentioned, or at least investigated by the support team/dev team, given the amount of posts and scope of users affected
Ive opened up ports and IP to WOW on router firewalls, turned everything off, even done a complete exposure to the net with no restrictions via virus killer etc.
Im starting to suspect its due to some geographic IPs not having proper Dual Stack conversion from IPv4 to IPv6 on services Blizzard have purchased, so it may be down to a 3rd party instead and not be us or them but rather someone else.
Either way, I’ve tried wow on a virgin system too, and still the same errors.
Its really unfair that their first response is to blame us without doing any background check on any of the forums to see if this is a common issue, and not one that has been passed on their Jira board (or whatever they use to manage tasks)
I dont think a simple copy + paste of ‘Check your connection’ or ‘disable addons and reset ui’ posts will resolve the issue, hence the deafening quiet.
you know what I hate the most? the labeling blizzard CS uses is outrageous, like you come here and label the problem as “oh its your Iranian ISP problem not ours”, “If you’re from Iran, we can’t help you…”. like what is this LOL!? why you have to make everything racist, what does being “Iranian” has to do with anything in a freaking video game???
1 Like
Mr Yh Taklol is worknig but i had 3k latency with it and i loaded oribos with my own internet connection with 75 latency but flying to bastion i got system message "Transfer Aborted: INstance not found " so yeah this game is unplayable.playing with vpn causes too much lag /// @blizzard do something
1 Like
Im from the UK and its happening here too
bump? help?
Its funny the other day I was tired and bored of getting dc and not being able to play game and was surfing blizzard’s site until I reached bunch of lies written here,
https://www.blizzard.com/en-us/company/about
words like “Every Voice Matters”, “Think Globally”, “Commit to Quality”, and so on… mean while many of us complaining about same problem since start of freaking shadowlands and no one hears our voice. this is pathetic and robbery at its finest.
5 Likes
Please do not bump or resurrect an older thread.