World of Warcraft Latency

Contributor

World of Warcraft Latency

I am posting here because I have already posted on the WoW forums and now wanted to post here. Many WoW players have been experiencing massive and unnaceptable latency. The tech upport at blizzard is saying the problem isn't entirely something on their end, so I was hoping someone would take a look at a trace route and maybe help me out some and possibly point out the problem? It looks to me that the latency goes up significantly once it hits the AT&T nodes.

 

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Owner>tracert 206.18.98.152

Tracing route to 206.18.98.152.tms-idc.com [206.18.98.152]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  206.18.98.152.tms-idc.com [206.18.98.152]
  2    11 ms     9 ms     8 ms  adsl-161-34-1.mia.bellsouth.net [74.161.34.1]
  3    12 ms    10 ms    12 ms  205.152.108.1
  4     8 ms     9 ms     5 ms  12.81.8.137
  5    12 ms    13 ms    10 ms  12.81.8.94
  6    11 ms    11 ms     6 ms  12.81.8.63
  7    14 ms    14 ms    13 ms  74.175.192.178
  8    50 ms    64 ms    59 ms  cr81.fldfl.ip.att.net [12.122.106.94]
  9    54 ms    61 ms    67 ms  cr2.ormfl.ip.att.net [12.122.1.45]
 10    56 ms    52 ms    49 ms  cr1.ormfl.ip.att.net [12.122.5.185]
 11    51 ms    50 ms    50 ms  cr2.attga.ip.att.net [12.122.31.29]
 12    51 ms    52 ms    51 ms  cr1.nsvtn.ip.att.net [12.122.28.106]
 13    55 ms    50 ms    51 ms  cr2.nsvtn.ip.att.net [12.122.28.70]
 14    51 ms    60 ms    65 ms  cr1.cl2oh.ip.att.net [12.122.28.74]
 15    50 ms    52 ms    56 ms  cr1.cgcil.ip.att.net [12.122.2.205]
 16    50 ms    49 ms    49 ms  cr83.cgcil.ip.att.net [12.123.7.109]
 17    52 ms    48 ms    49 ms  gar4.cgcil.ip.att.net [12.122.133.205]
 18    51 ms    52 ms    52 ms  12-122-254-202.attens.net [12.122.254.202]
 19    49 ms    51 ms    51 ms  63.240.130.202
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\Users\Owner>

Message 1 of 12 (6,438 Views)
Former Moderator

Re: World of Warcraft Latency

Hello Dolgorath ,

 

I extend my gratitude to you for contacting us about this issue through the forums and please, accept my sincere apologies for any inconvenience that you have experienced.

 

We would want to know the brand of your modem and if you are also having problems with Internet browsing . There are a lot of possible causes for getting latency . One of these would include getting slow speeds with your Internet Connection. To check your speed, please access www.speedtest.net and run a speed test from there. If ever you would get results that is lower than your speed plan, you can use this link for troubleshooting. http://www.att.com/esupport/article.jsp?sid=KB401526

 

It may also be caused by wrong incorrect DNS servers setup on your computer or router. Try to use these DNS servers and check if it lets you connect better .

Here is a link on how to do it .

http://www.att.com/esupport/article.jsp?sid=KB402035

 

It may also be caused by a third party firewall that is slowing down the game . You can try to adjust or disable the computer firewall's setting and see if it works better .

 

Adding the game to the router's firewall or opening firewall ports would also help . If the game does not show up automatically on your router's firewall, you can manually create a user-defined application profile. To do this, you will need to know the protocol and the port information.

You can also set the router to DMZ mode to open all the ports and make sure that the router's firewall is not slowing down the game. However it is not advisable since the the computer becomes less secure .

 

It would be best that you call us over the phone so we can help you troubleshoot this issue.

 

Should you need further help regarding your post, please feel free to reply on this thread or you may call our Technical Support Helpdesk. You may reach them at 1 888 321 2375 if you are from these states - KY, TN, NC, SC, LA, MS, AL, GA, FL; and 1 877 722 3755 if you are located in CA, NV, KS, MO, OK, AR, TX, WI, MI, IL, IN, OH, CT.

 

For quick answers, make the new AT&T Help site your first stop. Visit http://www.att.com/esupport/ where you'll find pages of product information to assist you.

 

Thank you for choosing AT&T where we value your Business.

 

Remember to always mark items that you find useful as "Accepted Solutions”, you can even mark multiple
posts
in a single thread.  This will help other users find this information too!!

Message 2 of 12 (6,405 Views)
Contributor

Re: World of Warcraft Latency

[ Edited ]


Please see the response from Time Warner Road Runner IT Dept regarding my loss of latency when I get to the ATT network.

{Personal content removed for your safety}

Dear William,

Thank you for contacting Time Warner Cable Road Runner technical E-mail support.

 

William, I can understand how important it is for you to have a consistent and stable Internet
connection.

I have checked the traceroute and latency is from 13th hop which is out of Road Runner netwok.

You will need to contact att.net to check if there is any issue at there server !

I hope the above information is useful.

William, in case you have any other concerns feel free to contact us with your previous
correspondence. It's a pleasure to have you as our valued customer.

For more information about Road Runner products and services, please visit our website
http://help.rr.com and check for online FAQs.

Your Case ID for this email is {Personal content removed for your safety}

 

Regards,

David R {Personal content removed for your safety}
Time Warner Cable,   
Road Runner Technical Support.

Original Message Follows: ------------------------

See the ping jump up @ 13


Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:
  1     6 ms     6 ms     8 ms  10.81.64.1
  2     6 ms     5 ms     6 ms  gig-2-4-nycmnys-rtr2.nyc.rr.com [24.29.100.41]
  3     6 ms     5 ms     6 ms  gig-2-0-0-nycmnya-rtr02.nyc.rr.com [24.29.98.26]
  4     9 ms    11 ms     9 ms  tenge-2-1-0-nycsnyoo-rtr1.nyc.rr.com [24.29.119.153]
  5     8 ms     7 ms     9 ms  66.109.6.76
  6     8 ms     7 ms    11 ms  ae-0-0.pr0.nyc30.tbone.rr.com [66.109.6.159]
  7    10 ms     8 ms     7 ms  xe-7-2-0.edge2.Newark1.Level3.net [4.59.20.33]
  8    20 ms    17 ms    17 ms  ae-31-51.ebr1.Newark1.Level3.net [4.68.99.30]
  9    10 ms    11 ms    10 ms  ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10    13 ms    16 ms    18 ms  ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]
11    10 ms    10 ms    12 ms  ae-3-89.edge3.NewYork1.Level3.net [4.68.16.145]
12     9 ms    10 ms     9 ms  192.205.37.69
13    77 ms    79 ms    77 ms  12.122.81.126
14    78 ms    79 ms    79 ms  cr2.cgcil.ip.att.net [12.122.1.2]
15    80 ms    81 ms    80 ms  cr1.cgcil.ip.att.net [12.122.2.53]
16    80 ms    80 ms    78 ms  cr2.dvmco.ip.att.net [12.122.31.85]
17    81 ms    83 ms    79 ms  cr1.slkut.ip.att.net [12.122.30.25]
18    79 ms    81 ms    85 ms  cr2.la2ca.ip.att.net [12.122.30.30]
19    78 ms    79 ms    80 ms  cr84.la2ca.ip.att.net [12.123.30.249]
20    83 ms    77 ms    78 ms  gar5.la2ca.ip.att.net [12.122.129.25]
21    81 ms    78 ms    84 ms  12.122.255.74
22    79 ms    77 ms    77 ms  12.129.193.242
23     *        *        *     Request timed out.
24  12.129.211.34  reports: Destination net unreachable.
Trace complete.

 


Tracing route to 12.129.255.52 over a maximum of 30 hops
  1     7 ms     6 ms     5 ms  10.81.64.1
  2     6 ms     8 ms     7 ms  gig-2-4-nycmnys-rtr1.nyc.rr.com [24.29.100.33]
  3     8 ms     6 ms     8 ms  gig-12-0-0-nycmnyrdc-rtr2.nyc.rr.com [24.29.113.218]
  4    10 ms     6 ms     8 ms  tenge-6-0-1-nwrknjmd-rtr.nyc.rr.com [24.29.96.234]
  5     8 ms     8 ms     7 ms  66.109.6.76
  6     9 ms    11 ms    10 ms  ae-0-0.pr0.nyc30.tbone.rr.com [66.109.6.159]
  7    12 ms    11 ms    20 ms  xe-4-2-0.edge2.Newark1.Level3.net [4.59.20.157]
  8    10 ms    16 ms    15 ms  ae-31-51.ebr1.Newark1.Level3.net [4.68.99.30]
  9    13 ms    11 ms     9 ms  ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10    18 ms    17 ms    17 ms  ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
11     9 ms    12 ms     9 ms  ae-1-69.edge3.NewYork1.Level3.net [4.68.16.17]
12     9 ms     9 ms     9 ms  192.205.37.69
13    78 ms    77 ms    78 ms  12.122.81.126
14    78 ms    80 ms    79 ms  cr2.cgcil.ip.att.net [12.122.1.2]
15    85 ms    78 ms    78 ms  cr1.cgcil.ip.att.net [12.122.2.53]
16    78 ms    79 ms    81 ms  cr2.dvmco.ip.att.net [12.122.31.85]
17    81 ms    78 ms    79 ms  cr1.slkut.ip.att.net [12.122.30.25]
18    79 ms    78 ms    79 ms  cr2.la2ca.ip.att.net [12.122.30.30]
19    81 ms    78 ms    78 ms  cr84.la2ca.ip.att.net [12.123.30.249]
20    80 ms    78 ms    80 ms  gar5.la2ca.ip.att.net [12.122.129.25]
21    81 ms    79 ms    80 ms  12.122.255.74
22   110 ms   207 ms   207 ms  12.129.193.242
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.
Trace complete.

 

 

Message 3 of 12 (6,217 Views)
Tutor

Re: World of Warcraft Latency

[ Edited ]

This looks like a good post to piggy back from, so I am having a similar issue, for the past month now my latency to wow servers has been getting increasingly worse, my normal MS is between 115-120 but for the last month its been 145-150 with peaks of 200

since last night however now I am peaking between 350-600+, I've contacted blizzard tech and they told me to contact my ISP, I contact my ISP and they tell me the increased ping is after it leaves them and hits ATT servers, and after going back and forth between my ISP (MTA in Alaska) and blizzard tech, I am finally coming here, my last hope to get this resolved. Here is a tracert to my server and a pathping to a server in the LA data center which is the closest to me.

 

Modem is a Zhone, router is a Dlink, i've done testing with 2 different modems with and without the router.

 


Tracing route to 12.129.254.183 over a maximum of 30 hops

  1    36 ms    33 ms    33 ms  254-214-137-216.mtaonline.net [216.137.214.254]
  2    32 ms    38 ms    32 ms  6506-2-er-ge3-2.mtaonline.net [216.152.176.181]
  3    32 ms    33 ms    33 ms  7606-2-er-po1.mtaonline.net [216.152.176.173]
  4    62 ms    62 ms    63 ms  66-193-100-29.static.twtelecom.net [66.193.100.29]
  5   135 ms    72 ms    73 ms  sea2-pr2-xe-1-3-0-0.us.twtelecom.net [66.192.253.122]
  6    71 ms    74 ms    72 ms  12.118.34.9
  7   100 ms    98 ms    98 ms  cr1.st6wa.ip.att.net [12.122.146.78]
  8    99 ms   102 ms   111 ms  cr2.sffca.ip.att.net [12.122.31.194]
  9    97 ms   100 ms    97 ms  cr2.la2ca.ip.att.net [12.122.31.133]
 10    95 ms    95 ms    95 ms  gar29.la2ca.ip.att.net [12.122.129.241]
 11    94 ms    95 ms    94 ms  12-122-254-234.attens.net [12.122.254.234]
 12     *       94 ms    93 ms  mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
 13     *        *        *     Request timed out.
 14     *     12.129.199.178  reports: Destination net unreachable.

Trace complete.

 

 

Tracing route to 206.18.98.184.tms-idc.com [206.18.98.184]
over a maximum of 30 hops:

  1    36 ms    32 ms    38 ms  254-238-137-216.mtaonline.net [216.137.238.254]
  2    36 ms    33 ms    36 ms  6506-2-er-ge3-2.mtaonline.net [216.152.176.181]
  3    34 ms    31 ms    32 ms  7606-1-er-ge1-1-3.mtaonline.net [216.152.176.225]
  4    73 ms    83 ms    71 ms  216.64.167.117
  5    71 ms    73 ms    74 ms  sea2-pr2-xe-0-3-0-0.us.twtelecom.net [66.192.243.34]
  6    74 ms    80 ms    71 ms  12.118.34.9
  7   122 ms   124 ms   125 ms  cr1.st6wa.ip.att.net [12.122.146.78]
  8   143 ms   124 ms   123 ms  cr1.cgcil.ip.att.net [12.122.31.161]
  9   170 ms   124 ms   225 ms  gar2.clboh.ip.att.net [12.122.133.197]
 10   120 ms   120 ms   125 ms  12.122.251.22
 11   128 ms   123 ms   125 ms  63.240.130.210

Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:

  1    37 ms    32 ms    34 ms  254-214-137-216.mtaonline.net [216.137.214.254]
  2    35 ms    32 ms    33 ms  6506-2-er-ge3-2.mtaonline.net [216.152.176.181]
  3    33 ms    33 ms    35 ms  7606-1-er-ge1-1-3.mtaonline.net [216.152.176.225]
  4    99 ms    78 ms    87 ms  216.64.167.117
  5    89 ms    78 ms    84 ms  sea2-pr2-xe-0-3-0-0.us.twtelecom.net [66.192.243.34]
  6    79 ms    79 ms    80 ms  12.118.34.9
  7   118 ms   127 ms   130 ms  cr1.st6wa.ip.att.net [12.122.146.78]
  8   107 ms   100 ms   116 ms  cr2.sffca.ip.att.net [12.122.31.194]
  9   112 ms   107 ms   111 ms  cr2.la2ca.ip.att.net [12.122.31.133]
 10   201 ms   167 ms   120 ms  gar29.la2ca.ip.att.net [12.122.129.241]
 11   102 ms     *      159 ms  12-122-254-238.attens.net [12.122.254.238]
 12   105 ms    98 ms    98 ms  mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
 13     *     12.129.211.38  reports: Destination net unreachable.

Trace complete.
 

and here is the pathping to the LA data center

 

 


Tracing route to 12.129.254.183 over a maximum of 30 hops

  0  Jeff-PC [192.168.0.199]
  1  254-214-137-216.mtaonline.net [216.137.214.254]
  2  6506-2-er-ge3-2.mtaonline.net [216.152.176.181]
  3  7606-2-er-po1.mtaonline.net [216.152.176.173]
  4  66-193-100-29.static.twtelecom.net [66.193.100.29]
  5  sea2-pr2-xe-1-3-0-0.us.twtelecom.net [66.192.253.122]
  6  12.118.34.9
  7  cr1.st6wa.ip.att.net [12.122.146.78]
  8  cr2.sffca.ip.att.net [12.122.31.194]
  9  cr2.la2ca.ip.att.net [12.122.31.133]
 10  gar29.la2ca.ip.att.net [12.122.129.241]
 11  12-122-254-238.attens.net [12.122.254.238]
 12  mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
 13     *        *     12.129.199.178  reports: Destination net unreachable.

Computing statistics for 325 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Jeff-PC [192.168.0.199]
                                0/ 100 =  0%   |
  1   34ms     0/ 100 =  0%     0/ 100 =  0%  254-214-137-216.mtaonline.net [216.137.214.254]
                                0/ 100 =  0%   |
  2   34ms     5/ 100 =  5%     5/ 100 =  5%  6506-2-er-ge3-2.mtaonline.net [216.152.176.181]
                                0/ 100 =  0%   |
  3   37ms     0/ 100 =  0%     0/ 100 =  0%  7606-2-er-po1.mtaonline.net [216.152.176.173]
                                0/ 100 =  0%   |
  4   72ms     0/ 100 =  0%     0/ 100 =  0%  66-193-100-29.static.twtelecom.net [66.193.100.29]
                                0/ 100 =  0%   |
  5   84ms     0/ 100 =  0%     0/ 100 =  0%  sea2-pr2-xe-1-3-0-0.us.twtelecom.net [66.192.253.122]
                                1/ 100 =  1%   |
  6   84ms     2/ 100 =  2%     1/ 100 =  1%  12.118.34.9
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%    99/ 100 = 99%  cr1.st6wa.ip.att.net [12.122.146.78]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%    99/ 100 = 99%  cr2.sffca.ip.att.net [12.122.31.194]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%    99/ 100 = 99%  cr2.la2ca.ip.att.net [12.122.31.133]
                                0/ 100 =  0%   |
 10  ---     100/ 100 =100%    99/ 100 = 99%  gar29.la2ca.ip.att.net [12.122.129.241]
                                0/ 100 =  0%   |
 11  ---     100/ 100 =100%    99/ 100 = 99%  12-122-254-238.attens.net [12.122.254.238]
                                0/ 100 =  0%   |
 12  116ms     1/ 100 =  1%     0/ 100 =  0%  mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
                               99/ 100 = 99%   |
 13  ---     100/ 100 =100%     0/ 100 =  0%  Jeff-PC [0.0.0.0]

Trace complete.

 

 

i really hope you guys can help as this has just been frustrating, thank you

 

Message 4 of 12 (4,536 Views)
Tutor

Re: World of Warcraft Latency

heres some more generated today (5/10)

 

Tracing route to 206.18.98.184.tms-idc.com [206.18.98.184]
over a maximum of 30 hops:

  1    32 ms    33 ms    32 ms  72.35.117.254
  2    33 ms    32 ms    31 ms  6506-1-er-ge3-2.mtaonline.net [216.152.176.205]
  3    33 ms    32 ms    32 ms  7606-1-er-po1.mtaonline.net [216.152.176.157]
  4    72 ms    71 ms    69 ms  216.64.167.117
  5    69 ms    75 ms    71 ms  sea2-pr2-xe-0-3-0-0.us.twtelecom.net [66.192.243.34]
  6    70 ms    68 ms    69 ms  12.118.34.9
  7   124 ms   124 ms   124 ms  cr1.st6wa.ip.att.net [12.122.146.78]
  8   124 ms   147 ms   129 ms  cr1.cgcil.ip.att.net [12.122.31.161]
  9   118 ms   120 ms   119 ms  gar2.clboh.ip.att.net [12.122.133.197]
 10   120 ms   119 ms   119 ms  12.122.251.22
 11   118 ms   117 ms   117 ms  63.240.130.210

 

 

Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:

  1    33 ms    32 ms    36 ms  72.35.117.254
  2    32 ms    33 ms    32 ms  6506-1-er-ge3-2.mtaonline.net [216.152.176.205]
  3    33 ms    32 ms    36 ms  7606-1-er-ge1-1-3.mtaonline.net [216.152.176.133]
  4    64 ms    63 ms    64 ms  66-193-100-29.static.twtelecom.net [66.193.100.29]
  5    63 ms    71 ms    64 ms  sea2-pr2-xe-1-3-0-0.us.twtelecom.net [66.192.253.122]
  6    64 ms    62 ms    63 ms  12.118.34.9
  7   100 ms   100 ms    99 ms  cr1.st6wa.ip.att.net [12.122.146.78]
  8   134 ms    98 ms   100 ms  cr2.sffca.ip.att.net [12.122.31.194]
  9    99 ms    99 ms    99 ms  cr2.la2ca.ip.att.net [12.122.31.133]
 10    94 ms    93 ms    94 ms  gar29.la2ca.ip.att.net [12.122.129.241]
 11    95 ms    94 ms    94 ms  12-122-254-234.attens.net [12.122.254.234]
 12    95 ms   114 ms   108 ms  mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
 13  12.129.211.34  reports: Destination net unreachable.

 

again my isp cant help me as this problem seems to be somewhere in your servers.

Message 5 of 12 (4,506 Views)
Tutor

Re: World of Warcraft Latency

do these threads even get answered

Message 6 of 12 (4,491 Views)
Tutor

Re: World of Warcraft Latency

well i give up, first post was 4 days ago, att tech support just seems pretty worthless and i am glad i dont have them for an ISP, its a shame that blizzard uses them for their servers because the customer support is just laughable.

Message 7 of 12 (4,479 Views)
Teacher

Re: World of Warcraft Latency

I know this is older post, but its something I see a lot and therefore I want to clear something up.

Just so everyone knows, its called ingress filtering.

What does that mean ? It means AT&T is filtering the packets. Let me repeat that : AT&T is filtering the packets. What does that mean then ? It means just because a traceroute does not get the full path, does not mean the routing is broken!

In short: Blizzard never fails to amaze me at their ignorance in technology. It isn't the route, and its as simple as that.

Message 8 of 12 (4,396 Views)
Highlighted
Contributor

Re: World of Warcraft Latency

Right... Frustration noted. What you said makes a lot of sense when the situation is like the one described above. I'm sure you are as angry as all the people who get annoyed by the constant lag in their connections. Nah... I don't think so. Now... how about this?

 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\costs>tracert 63.240.161.189

Tracing route to 63.240.161.189 over a maximum of 30 hops

  1    14 ms     7 ms     7 ms  10.34.0.1
  2     8 ms     9 ms     7 ms  187-123-126-72.pmebboco.eviaembratel.net.br [187
.122.126.72]
  3    10 ms     6 ms     9 ms  187-123-127-68.pmebboco.eviaembratel.net.br [187
.122.127.68]
  4    16 ms    15 ms    11 ms  embratel-G4-0-2-gacc15.spo.embratel.net.br [200.
213.208.133]
  5     9 ms     9 ms     9 ms  ebt-C2-core01.spo.embratel.net.br [200.230.243.1
7]
  6   374 ms   292 ms   231 ms  ebt-G0-3-5-1-tcore01.spo.embratel.net.br [200.23
0.251.169]
  7   245 ms   286 ms   245 ms  ebt-Bundle-POS1114-intl04.mianap.embratel.net.br
 [200.230.220.66]
  8   296 ms   266 ms   272 ms  sl-st30-mia-.sprintlink.net [144.223.64.221]
  9   272 ms   277 ms   270 ms  sl-crs1-mia-0-2-0-0.sprintlink.net [144.232.28.7
6]
 10   280 ms   258 ms   258 ms  192.205.32.141
 11   174 ms   174 ms   167 ms  12.122.155.170
 12   187 ms   172 ms   181 ms  cr2.ormfl.ip.att.net [12.122.1.45]
 13   351 ms   347 ms   340 ms  cr1.ormfl.ip.att.net [12.122.5.185]
 14   173 ms   172 ms   169 ms  cr2.attga.ip.att.net [12.122.31.29]
 15   486 ms   555 ms   490 ms  cr1.nsvtn.ip.att.net [12.122.28.106]
 16   168 ms   179 ms   165 ms  cr2.nsvtn.ip.att.net [12.122.28.70]
 17   168 ms     *      169 ms  cr1.cl2oh.ip.att.net [12.122.28.74]
 18   457 ms   482 ms   477 ms  cr1.cgcil.ip.att.net [12.122.2.205]
 19   484 ms   479 ms   468 ms  gar2.clboh.ip.att.net [12.122.133.197]
 20   465 ms   481 ms   471 ms  12.122.251.50
 21   499 ms   488 ms   473 ms  63.240.130.214
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\Users\costs>

 

 

Where's the issue?

@Blizzard?

@AT&T?

@Local Providers?

 

All those 3 are in the same cat bag and the clients just don't care whose fault it is, as long as it gets sorted out. Until at least one of the companies, if not all of them, step up and clearly inform what the problem is and inform an expected time for solution, all 3 of them will keep getting uglier and uglier in the eyes of their clients. That's shameful that nobody steps up to clarify and ridiculous if nobody is engaging to actually solve it...

 

it's been like that for weeks. Can someone step up and let us know what is going on?

Message 9 of 12 (3,841 Views)
Contributor

Re: World of Warcraft Latency

[ Edited ]

I'm getting terrible unplayable lag spikes all of the sudden. They're often so bad I get disconnected from the game. Here are a few tracerts to my WoW server (notice the random loss of response once it hits att, especially cr1.cgcil.ip.att.net):

 

Run #1:
Tracing route to 63.240.161.189 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1] 
  2     9 ms     8 ms     9 ms  73.110.72.1 
  3     8 ms     9 ms    10 ms  te-8-3-ur02.albuquerque.nm.albuq.comcast.net [68.85.224.5] 
  4     8 ms    14 ms    13 ms  te-8-4-ar02.albuquerque.nm.albuq.comcast.net [68.86.182.29] 
  5    31 ms    31 ms    32 ms  te-0-0-0-5-cr01.losangeles.ca.ibone.comcast.net [68.86.93.197] 
  6    32 ms    31 ms    36 ms  ps-0-0-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.86.58] 
  7    35 ms    32 ms    31 ms  192.205.37.25 
  8    63 ms    63 ms    63 ms  cr1.la2ca.ip.att.net [12.122.128.98] 
  9    65 ms    61 ms    63 ms  cr1.slkut.ip.att.net [12.122.30.29] 
 10    63 ms    64 ms    62 ms  cr2.dvmco.ip.att.net [12.122.30.26] 
 11     *        *       62 ms  cr1.cgcil.ip.att.net [12.122.31.86] 
 12     *       58 ms    57 ms  gar18.cgcil.ip.att.net [12.122.99.21] 
 13    59 ms    59 ms    59 ms  12.122.251.14 
 14    69 ms    80 ms    78 ms  63.240.130.206 
 15     *        *        *     Request timed out.
etc.


Run #2:
Tracing route to 63.240.161.189 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2    11 ms     7 ms     7 ms  73.110.72.1
  3     7 ms     7 ms     7 ms  te-8-3-ur02.albuquerque.nm.albuq.comcast.net [68.85.224.5]
  4    22 ms     8 ms     9 ms  te-8-4-ar02.albuquerque.nm.albuq.comcast.net [68.86.182.29]
  5    31 ms    32 ms    31 ms  te-0-0-0-5-cr01.losangeles.ca.ibone.comcast.net[68.86.93.197]
  6    36 ms    35 ms    31 ms  ps-0-0-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.86.58]
  7    30 ms    34 ms    39 ms  192.205.37.25
  8    63 ms    63 ms    59 ms  cr1.la2ca.ip.att.net [12.122.128.98]
  9    63 ms    63 ms    59 ms  cr1.slkut.ip.att.net [12.122.30.29]
 10    61 ms    60 ms    63 ms  cr2.dvmco.ip.att.net [12.122.30.26]
 11    59 ms    60 ms    60 ms  cr1.cgcil.ip.att.net [12.122.31.86]
 12    57 ms     *       58 ms  gar18.cgcil.ip.att.net [12.122.99.21]
 13    65 ms    61 ms    58 ms  12.122.251.14
 14    60 ms   204 ms   210 ms  63.240.130.206
 15     *        *        *     Request timed out.


Run #3:
Tracing route to 63.240.161.189 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2     7 ms     7 ms     7 ms  73.110.72.1
  3     8 ms    13 ms     9 ms  te-8-3-ur02.albuquerque.nm.albuq.comcast.net [68.85.224.5]
  4    13 ms    10 ms     9 ms  te-8-4-ar02.albuquerque.nm.albuq.comcast.net [68.86.182.29]
  5    32 ms    31 ms    36 ms  te-0-0-0-5-cr01.losangeles.ca.ibone.comcast.net[68.86.93.197]
  6    31 ms    31 ms    32 ms  ps-0-0-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.86.58]
  7    30 ms    31 ms    31 ms  192.205.37.25
  8    64 ms    64 ms    61 ms  cr1.la2ca.ip.att.net [12.122.128.98]
  9    65 ms    59 ms    64 ms  cr1.slkut.ip.att.net [12.122.30.29]
 10    63 ms    63 ms    59 ms  cr2.dvmco.ip.att.net [12.122.30.26]
 11    60 ms    63 ms    63 ms  cr1.cgcil.ip.att.net [12.122.31.86]
 12   144 ms   139 ms    74 ms  gar18.cgcil.ip.att.net [12.122.99.21]
 13    60 ms    62 ms    59 ms  12.122.251.14
 14    61 ms    59 ms    61 ms  63.240.130.206
 15     *        *        *     Request timed out.


Run #4:
Tracing route to 63.240.161.189 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2     7 ms     7 ms     9 ms  73.110.72.1
  3     9 ms    10 ms    11 ms  te-8-3-ur02.albuquerque.nm.albuq.comcast.net [68.85.224.5]
  4     8 ms     9 ms     9 ms  te-8-4-ar02.albuquerque.nm.albuq.comcast.net [68.86.182.29]
  5    31 ms    31 ms    31 ms  te-0-0-0-5-cr01.losangeles.ca.ibone.comcast.net[68.86.93.197]
  6    32 ms    31 ms    32 ms  ps-0-0-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.86.58]
  7    39 ms    34 ms    31 ms  192.205.37.25
  8    64 ms    63 ms    60 ms  cr1.la2ca.ip.att.net [12.122.128.98]
  9    60 ms    60 ms    59 ms  cr1.slkut.ip.att.net [12.122.30.29]
 10    61 ms    63 ms    59 ms  cr2.dvmco.ip.att.net [12.122.30.26]
 11    63 ms    59 ms    60 ms  cr1.cgcil.ip.att.net [12.122.31.86]
 12    61 ms    58 ms    60 ms  gar18.cgcil.ip.att.net [12.122.99.21]
 13    58 ms     *       59 ms  12.122.251.14
 14    60 ms    59 ms    59 ms  63.240.130.206
 15     *        *        *     Request timed out.


Run #5:
Tracing route to 63.240.161.189 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2     8 ms     9 ms    10 ms  73.110.72.1
  3     8 ms     8 ms     7 ms  te-8-3-ur02.albuquerque.nm.albuq.comcast.net [68.85.224.5]
  4     9 ms     9 ms    12 ms  te-8-4-ar02.albuquerque.nm.albuq.comcast.net [68.86.182.29]
  5    29 ms    31 ms    31 ms  te-0-0-0-5-cr01.losangeles.ca.ibone.comcast.net[68.86.93.197]
  6    34 ms    31 ms    31 ms  ps-0-0-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.86.58]
  7    34 ms    31 ms    35 ms  192.205.37.25
  8    62 ms    69 ms    63 ms  cr1.la2ca.ip.att.net [12.122.128.98]
  9    58 ms    59 ms    61 ms  cr1.slkut.ip.att.net [12.122.30.29]
 10    62 ms    60 ms    63 ms  cr2.dvmco.ip.att.net [12.122.30.26]
 11    61 ms    64 ms    63 ms  cr1.cgcil.ip.att.net [12.122.31.86]
 12    57 ms    61 ms    58 ms  gar18.cgcil.ip.att.net [12.122.99.21]
 13    82 ms   201 ms   208 ms  12.122.251.14
 14    62 ms    60 ms    61 ms  63.240.130.206
 15     *        *        *     Request timed out.


Run #6:
Tracing route to 63.240.161.189 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2     8 ms     9 ms     9 ms  73.110.72.1
  3     8 ms     9 ms    10 ms  te-8-3-ur02.albuquerque.nm.albuq.comcast.net [68.85.224.5]
  4    10 ms     9 ms     8 ms  te-8-4-ar02.albuquerque.nm.albuq.comcast.net [68.86.182.29]
  5    33 ms    32 ms    31 ms  te-0-0-0-5-cr01.losangeles.ca.ibone.comcast.net[68.86.93.197]
  6    34 ms    35 ms    35 ms  ps-0-0-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.86.58]
  7    30 ms    35 ms    32 ms  192.205.37.25
  8    69 ms    63 ms    67 ms  cr1.la2ca.ip.att.net [12.122.128.98]
  9    64 ms    63 ms    63 ms  cr1.slkut.ip.att.net [12.122.30.29]
 10    63 ms    63 ms    64 ms  cr2.dvmco.ip.att.net [12.122.30.26]
 11    65 ms     *       60 ms  cr1.cgcil.ip.att.net [12.122.31.86]
 12   104 ms    75 ms   149 ms  gar18.cgcil.ip.att.net [12.122.99.21]
 13    63 ms    59 ms    60 ms  12.122.251.14
 14    60 ms    60 ms    68 ms  63.240.130.206
 15     *        *        *     Request timed out.

 

This is unacceptable guys. Come on.

Message 10 of 12 (3,319 Views)
Teacher

Re: World of Warcraft Latency

You know what I find really amusing but also sad? First, as for the random loss of response once it hits cr1.cgcil.ip.att.net:

 

You show not one traceroute that has zero response from that node. The utility traceroute sends three probes per node, increasing the TTL (time to live) each node so that it can go one further node (traceroute was a rework of ping; it shows each node in the route and the time it took for each probe and *  if it times out - which is not to do with the TTL I might add). The TTL is to prevent infinite loops when there is a routing issue (e.g., once the TTL reaches zero  - decreasing each node - the routing is stopped). In other words: starts out with TTL of 1 and then receives a time-exceeded then increases it to 2 and now it checks the second node before it gets a time-exceeded.

 

HOWEVER, and this is important: just because a node does not respond does to a probe in a traceroute does not mean it is down or has a problem. The protocols that make up the Internet were never designed with security in mind and there have been many abuses of the error reporting protocol that ping uses (icmp). What is also unfortunate is some administrators filter icmp echo requests (pings) and as for your traceroute - well, Windows version (last I knew) uses ICMP by default. Also, as the man page (read: manual) of traceroute points out:

 

In the modern network environment the traditional traceroute methods can not be always applicable, because of widespread use of firewalls.  Such firewalls filter the "unlikely" UDP ports, or even ICMP echoes.  To solve this,
       some  additional tracerouting methods are implemented (including tcp), see LIST OF AVAILABLE METHODS below. Such methods try to use particular protocol and source/destination port, in order to bypass firewalls (to be seen by
       firewalls just as a start of allowed type of a network session).

 

(I'll add that even this is not completely fool proof). Also, to the person doing a traceroute to us.logon.battle.net [12.129.206.130] and got this:

 

13  12.129.211.34  reports: Destination net unreachable.

 

I hope you know that 12.129.211.34 is actually already at Blizzard's premises. It is true that AT&T owns the block 12.0.0.0 - 12.255.255.255 but much like local phone companies may use another carrier's equipment and resources the same applies here. So then Blizzard (in the case of 12.129.211.34) is in 12.129.192.0 - 12.129.255.255 which is part of AT&T managed services. But in the end 12.129.211.34 is:

CI - Blizzard Entertainment SID-8916 ATTWH-12-129-211-32-29-0807013652 (NET-12-129-211-32-1) 12.129.211.32 - 12.129.211.39

 

(meaning as much as AT&T itself is not filtering it all). Also observe that some times you'll get three *'s and then the next node will respond (which shows again that it's not true that one node is the problem and once it reaches three *'s its done).

 

Example is a traceroute I did to one of the nodes one or more than one have done traceroutes to (or part of a traceroute in my case):

 

 3  75.20.0.50 (75.20.0.50)  19.608 ms  21.152 ms  22.467 ms
 4  * * *
 5  * * *
 6  12.83.38.133 (12.83.38.133)  36.557 ms  35.448 ms  35.834 ms

 

 

 

Any way, if you can connect to the site then obviously tracing the route is not the only tool. Could there be latency caused at some point? Of course - that's a given. But the truth is that if you run into a host that accepts all kinds of probes or runs all kinds of services open to the public then someone who wants to compromise that host is going to have a fairly easy time.

Message 11 of 12 (3,305 Views)
Contributor

Re: World of Warcraft Latency

Got the same problem, 4 days having problem with huge latency, now I can't get in game, the internet is ok, i checked the connection speed etc. The huge problem is Blizzard says it's a ISP problem, ISP says it's a AT&T problem, and AT&T says...well AT&T says nothing, so I think they know that is an AT&T problem or maybe they just don't care, I'm not sure.

Message 12 of 12 (1,989 Views)
Share this topic
Announcements

Welcome to the AT&T Community Forums!!! Stop by the Community How-To section for tips on how to get started.