World of Warcraft. Unplayable latency.

Contributor

World of Warcraft. Unplayable latency.

[ Edited ]

Ok for the past week this has been occuring. Basically around 8-12PM the game becomes unplayable. I have Road Runner Cable, but the connection goes through your servers. When the connections reaches your servers that is when my ping spikes. Here is a Traceroute.

 

ISP: Bright house
Hernando County Florida
Tracing route to 206.18.198.212.tms-idc.com [206.18.98.212]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    25 ms    19 ms    24 ms  cpe-72-184-128-1.tampabay.res.rr.com [72.184.128
.1]
  3    13 ms    25 ms    19 ms  gig10-0-0-2062.tampfledc-rtr2.tampflrdc.rr.com [
65.32.37.170]
  4    12 ms    12 ms    15 ms  ge2-2-0.tampfledc-rtr4.tampflrdc.rr.com [65.32.1
3.66]
  5    21 ms    35 ms    16 ms  ae2s0-orld71-cbr2.noc.bhn.net [72.31.220.3]
  6    26 ms    39 ms    26 ms  ae-3-0.cr1.atl20.tbone.rr.com [66.109.6.104]
  7    24 ms    24 ms    32 ms  ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
  8    33 ms    27 ms    29 ms  if-1-1-0.har1.A56-Atlanta.as6453.net [64.86.8.21
]
  9    27 ms    34 ms    35 ms  Vlan60.icore1.A56-Atlanta.as6453.net [64.86.8.18
]
 10    25 ms    25 ms    37 ms  192.205.36.201
 11    60 ms    67 ms    76 ms  cr2.attga.ip.att.net [12.122.80.222]
 12   184 ms   187 ms   180 ms  cr1.nsvtn.ip.att.net [12.122.28.106]
 13    85 ms    83 ms    75 ms  cr2.nsvtn.ip.att.net [12.122.28.70]
 14    66 ms    79 ms    65 ms  cr1.cl2oh.ip.att.net [12.122.28.74]
 15     *       65 ms    60 ms  cr1.cgcil.ip.att.net [12.122.2.205]
 16    60 ms    62 ms    60 ms  cr83.cgcil.ip.att.net [12.123.7.109]
 17    65 ms    58 ms    61 ms  gar4.cgcil.ip.att.net [12.122.133.205]
 18   226 ms   194 ms   189 ms  12-122-254-202 begin_of_the_skype_highlighting              12-122-254-202      end_of_the_skype_highlighting.attens.net [12.122.254.202]
 19    82 ms    77 ms    73 ms  63.240.130.206
 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.
                               

Clearly the high ping and unplayable lag is at your fault. This needs to be fixed now. I am not the only player having this issue. Go on to the World of Warcraft's Techinical Support forums and you can see for yourself that many traceroutes are lagging when the information gets to your server. Blizzard said they are sticking with your servers because they like your service. Well how about sticking to that and fixing this please. You guys are making a lot of people angry.

 

Message 1 of 13 (5,581 Views)
Contributor

Re: World of Warcraft. Unplayable latency.

Can I please get a reply here. It is really affecting my gameplay.

Message 2 of 13 (5,485 Views)
Contributor

Re: World of Warcraft. Unplayable latency.

[ Edited ]

If you guys think it is only a handful of people having this problem. Here is the forum with 68 pages of posts.

http://us.battle.net/wow/en/forum/topic/1021054037?page=1

 

There is also another topic with around 100+ pages of the same issue. Please fix this ASAP.

Message 3 of 13 (5,450 Views)
Former Moderator

Re: World of Warcraft. Unplayable latency.

Hello Highjinx,

 

 

 

     Thank you for contacting our forum support and letting us know about this type of problem. I do apologize for the inconvenience if you are experiencing connection issues with regard to your game. As posted on your traceroute, you are referring to hops 11 to 18 that pass through the AT&T servers which generally provide high ping results. To begin with,  your server provider is Road runner cable. The AT&T servers that your packets reached were merely connection servers at that area.  You need to contact your Internet service provider and and verify why your packets run through an AT&T server.

 

 

Should you need further help regarding this post, please feel free to post your 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

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 4 of 13 (5,233 Views)
Contributor

Re: World of Warcraft. Unplayable latency.

[ Edited ]

pamelaz,

 

Are you aware that AT&T hosts the World of Warcraft servers?

 

http://news.bigdownload.com/2009/03/03/blizzard-renews-server-hosting-and-network-agreement-with-ata...

Message 5 of 13 (4,716 Views)
Contributor

Re: World of Warcraft. Unplayable latency.

its not just World of Warcraft,League of Legends and EQ 2 have same problem

 most of the games based on the west coast are routed through ATT, and past 6PM it becomes unplayable.

 

i am based on indiana and on road runner, and on the hop that routes through ATT my ping goes from 20-30 to 200

Message 6 of 13 (4,624 Views)
Contributor

Re: World of Warcraft. Unplayable latency.

I am an AT&T customer and this is a new problem that I have just begun having in the last couple of weeks.  The latency at times gets to over 1000 or I am completely disconnected and have to reboot the system to get back on again.  Since it doesn't happen every night and when it does it happens several times that night, I see no reason behind the problem as nothing has changed from my end.  I have been playing since Sept 2010 and this is the first time I have had any problems, but it is significant in the severity.  I mentioned it in my guild last night and was told that the problem was most likely with AT&T, so I began researching it this morning.  I am the only user on this account, so there isn't any competition in the household for bandwidth; and I haven't changed anything in the past few weeks which would have made any greater demand on the connection.  It is getting to be more than a minor inconvenience and needs to be corrected.

Message 7 of 13 (4,602 Views)
Contributor

Re: World of Warcraft. Unplayable latency.

im not on att internet .my last jump goes thru att nodes in dallas,, and before you say to ask my isp why it goes thru att, its because att hosts warcraft servers,, as you can clearly see in my tracert,, ATT IS TO BLAME FOR THE SEVERE LAG PROBLEM with several wow players... so why doesnt ATT step up an do something about it..

 

C:\Users\Tracy>tracert 206.18.98.220

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

  1     2 ms     2 ms     6 ms  F5d8233-4v3 [192.168.2.1]
  2    20 ms    18 ms    17 ms  ip-174-137-8-1.swatco.com [174.137.8.1]
  3    23 ms    16 ms    17 ms  172.30.3.69
  4    27 ms    21 ms    17 ms  ip-174-137-3-1.swatco.com [174.137.3.1]
  5    17 ms    17 ms    16 ms  iGWxo1-fltnCO.swatco.com [174.137.3.10]
  6    19 ms    26 ms    31 ms  iEGWxo1-dalIBX.swatco.com [174.137.3.193]
  7    31 ms    32 ms    34 ms  209.234.254.133
  8    20 ms    21 ms    41 ms  67.17.192.253
  9   343 ms   349 ms   353 ms  att-1-ar2.CHI2.gblx.net [64.208.110.146]
 10   351 ms   361 ms   349 ms  cr2.cgcil.ip.att.net [12.122.81.98]
 11   351 ms   349 ms   360 ms  cr83.cgcil.ip.att.net [12.123.7.109]
 12   795 ms   800 ms   853 ms  gar4.cgcil.ip.att.net [12.122.133.205]
 13   749 ms   751 ms     *     12-122-254-202.attens.net [12.122.254.202]
 14   751 ms     * ms   649 ms  63.240.130.202
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.

Message 8 of 13 (4,209 Views)
Contributor

Re: World of Warcraft. Unplayable latency.

Dear Mr or Ms ATT support agent.  On numerous occasions i have called your support desk.  on numberous occasions i have been told that my ATT cannot do anything about problems related to this game.  On numerous occasions i mentioned "YOU GUYS ARE RESPONSIBLE FOR THE GAME SERVERS IN DALLAS" so first off...  Either confirm or deny that ATT does infact maintain the Blizzard Entertainment World of Warcraft servers, in my case spefically the one in the Dallas area.  Secondly, my latency is 200 plus at any given time and i am using ATT DSL, and i am less than 70 miles from the Dallas Datacenter.  Last but not lease, my guildmates i play with some of which live in CANADA, have 30 to 40 latency.  So your telling me and all the people on this forum that we should contact our ISP?  I DID!  you did nothing, you sent out a tech to check my line, no problems on my line, BUT I TOLD YOU THAT!  the increase was somewhere between Cleburne and Dallas.  So i have contacted my ISP several times, oddly every inch of this problem is directly controlled by ATT.  Who will you pass the buck to now?   Btw, this is not an inconvenience as forementioned, this is jsut plain gross neglegence on your part for not taking care of the customers have made ATT what it is today.

Message 9 of 13 (4,202 Views)
Contributor

Re: World of Warcraft. Unplayable latency.

Allow me to correct myself.  I transferred to Malygos server (Dallas server)  a while back to drop the latency i was having before.  Malygos is now a Chicago server, yes i am aware.

Message 10 of 13 (4,200 Views)
Tutor

Re: World of Warcraft. Unplayable latency.

I've been experiencing the same issues for over two months now.  

 

I've included a fresh traceroute and pathping, during which, my in-game latency was showing 56ms home, 2481ms world.

 

Tracing route to 206.18.149.14 over a maximum of 30 hops

  1     8 ms     9 ms     9 ms  10.11.96.1
  2     8 ms     9 ms    10 ms  68.10.10.173
  3     8 ms     9 ms    12 ms  172.22.48.157
  4    10 ms     8 ms     9 ms  68.10.8.157
  5    11 ms    15 ms    12 ms  68.1.4.139
  6    14 ms    12 ms    16 ms  192.205.32.125
  7   108 ms   126 ms   113 ms  cr2.cgcil.ip.att.net [12.122.132.158]
  8   117 ms   103 ms   171 ms  gar3.cgcil.ip.att.net [12.122.132.213]
  9   105 ms   112 ms   137 ms  12.122.251.22
 10   181 ms   121 ms   131 ms  63.240.130.214
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *     ^C

 

Tracing route to 206.18.149.14 over a maximum of 30 hops

  1  10.11.96.1
  2  68.10.10.173
  3  172.22.48.157
  4  68.10.8.157
  5  68.1.4.139
  6  192.205.32.125
  7  cr2.cgcil.ip.att.net [12.122.132.158]
  8  gar3.cgcil.ip.att.net [12.122.132.213]
  9  12.122.251.22
 10  63.240.130.214
 11     *        *        *
Computing statistics for 275 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  1    7ms     0/ 100 =  0%     0/ 100 =  0%  10.11.96.1
                                0/ 100 =  0%   |
  2    9ms     0/ 100 =  0%     0/ 100 =  0%  68.10.10.173
                                0/ 100 =  0%   |
  3   11ms     0/ 100 =  0%     0/ 100 =  0%  172.22.48.157
                                0/ 100 =  0%   |
  4   12ms     0/ 100 =  0%     0/ 100 =  0%  68.10.8.157
                                0/ 100 =  0%   |
  5   15ms     0/ 100 =  0%     0/ 100 =  0%  68.1.4.139
                                0/ 100 =  0%   |
  6   16ms     0/ 100 =  0%     0/ 100 =  0%  192.205.32.125
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%   100/ 100 =100%  cr2.cgcil.ip.att.net [12.122.132.158]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%   100/ 100 =100%  gar3.cgcil.ip.att.net [12.122.132.213]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%   100/ 100 =100%  12.122.251.22
                                0/ 100 =  0%   |
 10  141ms     0/ 100 =  0%     0/ 100 =  0%  63.240.130.214

Trace complete.

 ISP: Cox Communications

 Modem: Arris TM602G

 

Before I am given the whole "You need to contact your ISP" spiel, I have done this already, several times.  I've had my ISP run every diagnostic that is possible, the issue is not on my ISP's end.  My ISP has directed me here after several attempts from Tier 2 and 3 techs at Cox Communications attempting to contact AT&T have lead to nothing but "You need to verify that you need to access these servers across the AT&T network.  These servers are for AT&T customer use only, non-AT&T customers should not have their data crossing them." (Phone conversation on 10/19/2011 with AT&T and Cox Communications).  

As far as I am aware, AT&T is who Blizzard Entertainment leases out data center space for their servers, and provides their servers network access.  This means that there is no other route to these servers that DOES NOT involve crossing the AT&T network.

Message 11 of 13 (3,641 Views)
Tutor

Re: World of Warcraft. Unplayable latency.

[ Edited ]
 
 
 
 
 
 This is all happening again.
 
 

This is a 5 hour MTR from Axtel (Mexico) ISP when playing WoW on a NY datacenter.

 
 

Only problem is with WoW on those datacenters.

 

 

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                            192.168.15.1 -   29 | 21581 | 15459 |    0 |    0 |    2 |    0 |

|            200-56-0-1.dynamic.axtel.net -   29 | 21709 | 15457 |    1 |    1 |   75 |    2 |

|                          189.213.107.34 -   34 | 23347 | 15442 |    1 |    2 |  304 |    3 |

|ifwa-ln3-201-140-38-178.mtyxl.static.axtel.net -   33 | 22833 | 15456 |    1 |    5 |  197 |    4 |

|    te4-1.ccr01.mty01.atlas.cogentco.com -   34 | 22941 | 15342 |   19 |   49 |  423 |   19 |

|    te3-2.ccr01.mfe01.atlas.cogentco.com -   29 | 21750 | 15452 |   19 |   51 |  440 |   19 |

|te0-3-0-4.mpd22.iah01.atlas.cogentco.com -   42 | 26430 | 15451 |   23 |   24 |  103 |   25 |

|te0-1-0-6.mpd22.atl01.atlas.cogentco.com -   33 | 22904 | 15404 |   37 |   38 |  255 |   39 |

|te0-4-0-7.mpd22.dca01.atlas.cogentco.com -   30 | 21950 | 15447 |   48 |   49 |  126 |   50 |

|te0-1-0-1.mpd22.iad02.atlas.cogentco.com -   34 | 23267 | 15438 |   49 |   50 |  357 |   50 |

|                          192.205.37.105 -   33 | 20309 | 13711 |   83 |   95 |  232 |  101 |

|                    cr1.wswdc.ip.att.net -   33 | 20356 | 13776 |   91 |  101 |  338 |  109 |

|                    cr2.phlpa.ip.att.net -   33 | 20348 | 13756 |   91 |  101 |  251 |  108 |

|           Destination host unreachable. -   11 | 15290 | 13760 |   89 |  106 |  335 |   98 |

|                            12.122.251.2 -   33 | 20356 | 13781 |   96 |  111 |  633 |  265 |

|mdf001c7613r0003-gig-10-1.nyc3.attens.net -   32 | 20334 | 13856 |   89 |  110 |  559 |   98 |

|                   No response from host -  100 | 4388 |    0 |    0 |    0 |    0 |    0 |

|           Destination host unreachable. -  100 | 4282 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 | 4386 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 | 4388 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 | 4387 |    0 |    0 |    0 |    0 |    0 |

|           Destination host unreachable. -  100 | 4282 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 | 4386 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 | 4386 |    0 |    0 |    0 |    0 |    0 |

|           Destination host unreachable. -  100 | 4389 |    0 |    0 |    0 |    0 |    0 |

|           Destination host unreachable. -  100 | 4282 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 | 4386 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 | 4387 |    0 |    0 |    0 |    0 |    0 |

|           Destination host unreachable. -  100 | 4392 |    0 |    0 |    0 |    0 |    0 |

|           Destination host unreachable. -  100 | 4282 |    0 |    0 |    0 |    0 |    0 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

 
 
 
Message 12 of 13 (2,457 Views)
Tutor

Re: World of Warcraft. Unplayable latency.

[ Edited ]

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            192.168.15.1 -    0 |   10 |   10 |    0 |    0 |    1 |    1 |
|            200-56-0-1.dynamic.axtel.net -    0 |   10 |   10 |    3 |    5 |    9 |    3 |
|                          189.213.107.34 -    0 |   10 |   10 |    2 |    3 |    6 |    4 |
|ifwa-ln3-201-140-38-178.mtyxl.static.axtel.net -    0 |   10 |   10 |    4 |    5 |    7 |    7 |
|    te4-1.ccr01.mty01.atlas.cogentco.com -    0 |   10 |   10 |   21 |   23 |   28 |   21 |
|    te3-2.ccr01.mfe01.atlas.cogentco.com -    0 |   10 |   10 |   19 |   22 |   25 |   19 |
|te0-3-0-4.mpd22.iah01.atlas.cogentco.com -    0 |   10 |   10 |   23 |   26 |   31 |   24 |
|te0-1-0-6.mpd22.atl01.atlas.cogentco.com -    0 |   10 |   10 |   39 |   39 |   41 |   40 |
|te0-4-0-7.mpd22.dca01.atlas.cogentco.com -    0 |   10 |   10 |   50 |   52 |   56 |   52 |
|te0-1-0-1.mpd22.iad02.atlas.cogentco.com -    0 |   10 |   10 |   51 |   52 |   55 |   52 |
|                          192.205.37.105 -    0 |   10 |   10 |   77 |   95 |  149 |   93 |
|                    cr1.wswdc.ip.att.net -    0 |   10 |   10 |   88 |   98 |  104 |  100 |
|                    cr2.phlpa.ip.att.net -    0 |   10 |   10 |   85 |   97 |  108 |  103 |
|                   gar1.pitpa.ip.att.net -    0 |   10 |   10 |   83 |  103 |  170 |  170 |
|                            12.122.251.2 -    0 |   10 |   10 |   93 |  105 |  109 |  105 |
|mdf001c7613r0003-gig-10-1.nyc3.attens.net -    0 |   10 |   10 |   84 |   95 |  101 |  100 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Message 13 of 13 (2,366 Views)