NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| reply to dietro
Re: High Latency in WoW, North Florida to Boston
said by dietro  :First of all Norman, I've not pointed a finger at anyone. I'm asking for help (not condescension). Secondly, I'm sure you're right that the issue is out of my control. But since I cant stand playing world of lagcraft I have alot of time on my hands to post these threads on any forum I can find. Couple questions for you: 1. Is there no way that I can contact ATTW? You are not their customer; odds are, even if you found a POC, they'd not listen.
2. Is blizzard connected thru DSL? and if so are they interleaved also?
More likely through some sort of link like an OCnn link; depends upon who, exactly, is providing their hosting. They have way too many gamers to be relying on an asymmetric DSL provider.
3. Is there absolutely no way that I can be routed around those particular ATTW routers?
Routing depends upon BGP announcement by the destination. If Blizzard is either hosted on ATTW, or their hosting provider only has upstream transit from ATTW, then you have to go through ATTW.
A friend on the server is with Roadrunner, his last hop is "in-addr.arpa [12.130.0.174]" (even though he first goes thru a few att hops) and his in-game latency is fine.
Hop 'in-addr.arpa [12.130.0.174]' is an AT&T IP address (ATTW owns the entire Class A: 12.0.0.0 subnet 255.0.0.0). An ARIN 'whois' lookup shows that IP address on a 'SWIP' assignment to an outfit called, "CERFnet"; which means that CERFnet is paying for a block of IP addresses from AT&T:
Your trace routes to the Boston WoW server are on SWIP to Blizzard Entertainment from CERFnet:
I have traced route to WoW login servers in Southern California, which are ultimately hosted on AT&T; either "Worldnet Services", or just plain "Services" (I don't recall if the destination was ATTW, or ATTS).
My best guess is that Blizzard Entertainment is AT&T's customer (either directly, or through CERFnet), and they would have the best handle on how to improve the situation. Assuming they don't play the finger pointing game, and lay the blame on the residential networks you are using to get onto the Internet.
P.S. FYI, AT&T is a very large corporation, which was bought by SBC in 2006. After which, SBC changed their corporate ID from, "SBC", to, "AT&T". There are several operating divisions. Nearly as I can tell, they sell commercial hosting through, "AT&T Services". They provide national transit backbone service through, "AT&T Worldnet Services". The parent corporation, which used to be SBC, sells residential transit through, "AT&T Internet Services". And, since 2007, when AT&T bought Bellsouth, also residential transit through 'bellsouth.net' routers. Being a customer of "AT&T FastAcces DSL" service does not make you a customer of "AT&T Worldnet Services", or of "AT&T Services".
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| It is probably somewhat more complicated than that. I am always forgetting about the return path issue. Packets not only travel from you to the server, but also come back. The return path isn't always the same as the forward path. If you can find someone at WoW willing to run a trace route to you, and you compare his trace to you with your trace to the server, you may see a significant difference.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
