01/22/2013 07:34 PMPosted by HowlzHe 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”.
Just to note here. Blizzard disable responding to Traceroute type packets past the gateway into their network for security reasons.
Essentially it's mainly to guard against ping flood attacks as well as to stop people from guessing the internal struture of their network. This is a standard thing to do in the IT industry.
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 actually feels more like a Bug to me.
In software design you can never predict a bug coming up.
Back about a week or so ago a #114 error was pretty rare - it would come up in a handful of cases only. So rarely that I never really had a chance to diagnose why it was happening.
Fast forward to now and I'm seeing tons of threads on it even a sticky in the Tech Support forums on it. They don't usually do that for specific cases of errors.
And no offence intended here but surely in your reading you've coming across cases where people have been able to resolve their #114 error themselves ? That in itself suggests it's a more complex error then simply thinking it's all on Blizzard's side.