Quote Originally Posted by Allyra View Post
snip
I see what you're saying, I do. But they way traffic routes and the way the entire structure is laid out wouldn't support the argument.

It's not Squares end. Their control starts and stops in Montreal (network wise). I'll show you (early hops omitted due to being behind my companies firewall):




Look at hop 6. I have an asterisk. This is command prompt saying that on the third poll, it could establish/verify the latency at that specific hop. Hop 6 happens to be in Seattle and is managed by Level3. Level3 is doing okay today, but has had issues in the past week: http://www.internetpulse.net/

That "data center" (it's actually a node) isn't managed by Square. Level3 is a Tier 1 backbone and are their own company that doesn't know that SE even exists. They are completely separate companies that do completely different things. It's unreasonable to expect Square to get on the phone to Level3 and say "hey, can you fix that node? Our players are having issues". Level3 would laugh them right off the phone and Square couldn't do anything about it.

Check hops 13-15. Now, these ARE Square's servers and internal route paths. If you see a spike in latency or asterisks here, then yeah, Square's bad.

This is just my route path. I'm one person out of MILLIONS that use the internet a day. Traffic ebbs and flows. There is literally nothing Square can do to fix a node that doesn't belong to them.

Find the break in the connection and run it back to the ISP that manages it. This is the only realistic way to fix the core problem.

WoW has better ROUTE paths. They probably have a contract with their ISP and full fiber connections to every switch. I'm sure Square asked for it. It's up to Ormuco (their ISP) to trench it.