Hi Machkhan, no I have not.
I cannot find anywhere where Blizzard has said ‘yes, this was the problem and here is THE FIX in the next maintenance’. Rather, it has been ‘here are some WORK-A-ROUNDS. Try this, try that. MAYBE this will work, MAYBE that will work. Good luck with that and have a nice day’. I am waiting for THE FIX, not a list of ‘cross your fingers and try this’. Have you checked the forums today? People are STILL posting that they have issues with 114.
As stated, I am not techno savvy and with a house full of people with computers, smartphones, tablets and an endless list of gadgets that rely on connection to the net, there is no way I am going to fiddle with settings I don’t understand.
Your suggestion that I contact my ISP is what triggered the thought of looking up my old guildies. Why phone their Contact Centre and get some person that will not understand my problem when I can just phone an actual technician AND who actually has played the game ??
Anyway, they did discuss it with co-workers and the Contact Centre has received numerous calls from customers stating the 114 issue and that Blizzard told them to call as it’s the ISP’s fault….
My guildie mate is going home tonight and is going to re-activate his, and his family’s WoW accounts. He has five identically specced computers at home and will see if the 114 issue can be replicated on his comps. He is a geek and loves this stuff so no biggie I guess. If any of his comps are affected he will have something to physically investigate.
He noted, that in another thread on the same issue that he read, that someone highlighted the fact that almost all “trace routes” (I have no idea what that is) no matter where they originated from in Australasia all lost their connection at one specific spot in the US. He considered that a rather “odd coincidence”. Also in that same thread another poster stated they had talked to their ISP in Australia and posted their response. That ISP also seems to think it cannot be a logical fault of the ISPs – even went as far to site it had to have come from work Blizzard had done to their systems.
Sorry, but this seems to make more sense to me. I am in Project Management, and if I was rolling out significant new changes into my customer’s network I would test it on a small group first (smallest group of customers for Blizz is Australasia). This is the logical thing to do, and in Project Management, is exactly what I would do. Rolling out significant changes to your largest group base (for Blizz that is North America) and it falling over is not an option.
This scenario seems to make more sense to me about what has probably happened.
It would be very interesting when this current maintenance routine is over, and suddenly there is no 114 error.
Anyway, will see what happens on the other side of the maintenance. If the 114 error is still around, hopefully my guildie mate gets it on at least one of his computers and then can take it into his ISP Test Labs and start to pull it apart.
Edited by Howlz on 1/22/2013 7:36 PM PST