100s of posts on WoW Tech forums

Highlighted
Contributor

100s of posts on WoW Tech forums

All having the same problem all with about the same traceroute problems, All on different ISPs. This is on your part, FIX IT.

 

Tracing route to us.logon.battle.net [12.129.206.130]

over a maximum of 30 hops:



  1     1 ms     1 ms     1 ms  192.168.1.1

  2     *       12 ms     9 ms  L100.NWRKNJ-VFTTP-94.verizon-gni.net [98.109.129.1]

  3    10 ms    12 ms    11 ms  G2-0-5-894.NWRKNJ-LCR-08.verizon-gni.net [130.81.110.86]

  4    23 ms    17 ms    21 ms  so-5-0-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.29.10]

  5    15 ms    16 ms    15 ms  xe-6-1-3-0.NY325-BB-RTR2.verizon-gni.net [130.81.23.234]

  6    14 ms    14 ms    15 ms  192.205.36.57

  7   114 ms   169 ms   117 ms  cr1.n54ny.ip.att.net [12.122.86.6]

  8     *      131 ms   113 ms  cr2.cgcil.ip.att.net [12.122.1.2]

  9   102 ms     *        *     cr1.cgcil.ip.att.net [12.122.2.53]

 10   111 ms    97 ms   109 ms  cr2.dvmco.ip.att.net [12.122.31.85]

 11     *      124 ms   127 ms  cr1.slkut.ip.att.net [12.122.30.25]

 12   118 ms   120 ms   113 ms  cr2.la2ca.ip.att.net [12.122.30.30]

 13   140 ms   105 ms   109 ms  cr84.la2ca.ip.att.net [12.123.30.249]

 14     *      193 ms     *     gar5.la2ca.ip.att.net [12.122.129.25]

 15   117 ms     *        *     12.122.255.74

 16    94 ms    97 ms   106 ms  mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]

 17  12.129.206.130  reports: Destination net unreachable.



Trace complete.

381 Views
Message 1 of 2
Tutor

Re: 100s of posts on WoW Tech forums

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 2 of 2
You must type a description before you click preview or reply.
Share this topic
Announcements

Welcome to the internet boards! Did you know the AT&T Community forums has the answers you need to solve most service woes? Check out our How To Forum article. You will learn how to find your answer!

Service acting up? Click here to troubleshoot now!

For DSL related issues. We highly recommend chatting with our teams to address this as quickly as possible.

Additional Support