Bad Latency +Tracert -> att.net/attens Slow

85 Troll Druid
3775
see tracert in first reply, and fourth reply.

Two Tracerts to the logon server while having high reported latencies in WoW. This has happened before. Also important to know that the latency comes in spikes. I would appreciate speculation from anyone about where I could start complaining to on monday morning. I'm supposed to raid tonight and tommorow night :(

Metrocast is my ISP.

Anywhere else I can go to learn what this stuff means?

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

over a maximum of 30 hops:



1 9 ms 6 ms 6 ms 10.206.216.1

2 7 ms 8 ms 6 ms static-216-36-30-225.cpe.metrocast.net [216.36.30.225]

3 9 ms 8 ms 30 ms static-216-36-30-202.cpe.metrocast.net [216.36.30.202]

4 14 ms 24 ms 7 ms static-216-36-30-201.cpe.metrocast.net [216.36.30.201]

5 13 ms 10 ms 10 ms border7.tge1-4.harron-3.wdc002.pnap.net [63.251.92.161]

6 19 ms 15 ms 89 ms core2.te5-2-bbnet2.wdc002.pnap.net [216.52.127.72]

7 132 ms 15 ms 152 ms TenGigE0-3-4-0.GW1.IAD8.ALTER.NET [152.179.50.53]

8 157 ms 12 ms 15 ms 0.xe-3-1-2.XL3.IAD8.ALTER.NET [152.63.35.146]

9 16 ms 172 ms 39 ms 0.ae3.BR1.IAD8.ALTER.NET [152.63.33.117]

10 13 ms 13 ms 14 ms 192.205.36.141

11 84 ms 85 ms 219 ms cr2.wswdc.ip.att.net [12.122.81.250]

12 124 ms 98 ms 82 ms cr1.cgcil.ip.att.net [12.122.18.21]

13 79 ms 79 ms 81 ms cr2.dvmco.ip.att.net [12.122.31.85]

14 84 ms 85 ms 88 ms cr1.slkut.ip.att.net [12.122.30.25]

15 95 ms 171 ms 94 ms cr2.la2ca.ip.att.net [12.122.30.30]

16 145 ms 85 ms 86 ms cr84.la2ca.ip.att.net [12.123.30.249]

17 85 ms 94 ms 145 ms gar5.la2ca.ip.att.net [12.122.129.25]

18 91 ms 83 ms 83 ms 12.122.255.74

19 83 ms 79 ms 81 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]

20 12.129.211.34 reports: Destination net unreachable.



Trace complete.



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

over a maximum of 30 hops:



1 11 ms 7 ms * 10.206.216.1

2 116 ms 7 ms 7 ms static-216-36-30-225.cpe.metrocast.net [216.36.30.225]

3 6 ms 7 ms 7 ms static-216-36-30-202.cpe.metrocast.net [216.36.30.202]

4 7 ms 50 ms 8 ms static-216-36-30-201.cpe.metrocast.net [216.36.30.201]

5 22 ms 14 ms 68 ms border7.tge1-4.harron-3.wdc002.pnap.net [63.251.92.161]

6 50 ms 18 ms 11 ms core2.te5-2-bbnet2.wdc002.pnap.net [216.52.127.72]

7 24 ms 9 ms 10 ms TenGigE0-3-4-0.GW1.IAD8.ALTER.NET [152.179.50.53]

8 13 ms 84 ms 12 ms 0.xe-3-1-2.XL3.IAD8.ALTER.NET [152.63.35.146]

9 14 ms 10 ms 64 ms 0.ae3.BR1.IAD8.ALTER.NET [152.63.33.117]

10 16 ms 11 ms 12 ms 192.205.36.141

11 83 ms 168 ms 197 ms cr2.wswdc.ip.att.net [12.122.81.250]

12 78 ms 81 ms * cr1.cgcil.ip.att.net [12.122.18.21]

13 83 ms 78 ms 79 ms cr2.dvmco.ip.att.net [12.122.31.85]

14 192 ms 84 ms 83 ms cr1.slkut.ip.att.net [12.122.30.25]

15 85 ms 84 ms 144 ms cr2.la2ca.ip.att.net [12.122.30.30]

16 74 ms 74 ms 75 ms cr84.la2ca.ip.att.net [12.123.30.249]

17 119 ms 82 ms 81 ms gar5.la2ca.ip.att.net [12.122.129.25]

18 83 ms 85 ms 84 ms 12.122.255.74

19 234 ms 226 ms 106 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]

20 12.129.211.34 reports: Destination net unreachable.



Trace complete.
Edited by Beardozer on 3/27/2011 9:04 AM PDT
Reply Quote
85 Troll Druid
3775
This one I was doing while I thought my latency was good because I wanted to supply a good one here. However WoW DC'd in the middle of it.




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

over a maximum of 30 hops:



1 8 ms 8 ms 6 ms 10.206.216.1

2 13 ms 11 ms 7 ms static-216-36-30-225.cpe.metrocast.net [216.36.30.225]

3 12 ms 11 ms 17 ms static-216-36-30-202.cpe.metrocast.net [216.36.30.202]

4 24 ms 20 ms 26 ms static-216-36-30-201.cpe.metrocast.net [216.36.30.201]

5 40 ms 48 ms 34 ms border7.tge1-4.harron-3.wdc002.pnap.net [63.251.92.161]

6 33 ms 31 ms 34 ms core2.te5-2-bbnet2.wdc002.pnap.net [216.52.127.72]

7 42 ms 33 ms 32 ms TenGigE0-3-4-0.GW1.IAD8.ALTER.NET [152.179.50.53]

8 276 ms 291 ms 32 ms 0.xe-3-1-2.XL3.IAD8.ALTER.NET [152.63.35.146]

9 47 ms 32 ms 171 ms 0.ae3.BR1.IAD8.ALTER.NET [152.63.33.117]

10 33 ms 141 ms 33 ms 192.205.36.141

11 107 ms 106 ms 208 ms cr2.wswdc.ip.att.net [12.122.81.250]

12 103 ms * 190 ms cr1.cgcil.ip.att.net [12.122.18.21]

13 205 ms 114 ms 100 ms cr2.dvmco.ip.att.net [12.122.31.85]

14 103 ms 196 ms 96 ms cr1.slkut.ip.att.net [12.122.30.25]

15 105 ms 114 ms 204 ms cr2.la2ca.ip.att.net [12.122.30.30]

16 221 ms 200 ms 94 ms cr84.la2ca.ip.att.net [12.123.30.249]

17 106 ms 106 ms 105 ms gar5.la2ca.ip.att.net [12.122.129.25]

18 231 ms * 100 ms 12.122.255.74

19 191 ms 99 ms 97 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]

20 12.129.211.34 reports: Destination net unreachable.



Trace complete.
Reply Quote
85 Troll Druid
3775
Anyone speculate? I'd like to know where to start :(

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

over a maximum of 30 hops:



1 11 ms 134 ms 7 ms 10.206.216.1

2 16 ms 7 ms 195 ms static-216-36-30-225.cpe.metrocast.net [216.36.30.225]

3 172 ms 13 ms 189 ms static-216-36-30-202.cpe.metrocast.net [216.36.30.202]

4 172 ms 202 ms 12 ms static-216-36-30-201.cpe.metrocast.net [216.36.30.201]

5 24 ms 10 ms 154 ms border7.tge1-4.harron-3.wdc002.pnap.net [63.251.92.161]

6 14 ms 10 ms 100 ms core2.te5-2-bbnet2.wdc002.pnap.net [216.52.127.72]

7 14 ms 11 ms 11 ms TenGigE0-3-4-0.GW1.IAD8.ALTER.NET [152.179.50.53]

8 13 ms 16 ms 16 ms 0.xe-3-1-2.XL3.IAD8.ALTER.NET [152.63.35.146]

9 21 ms 9 ms 9 ms 0.ae3.BR1.IAD8.ALTER.NET [152.63.33.117]

10 58 ms 59 ms 38 ms 192.205.36.141

11 90 ms 84 ms 84 ms cr2.wswdc.ip.att.net [12.122.81.250]

12 252 ms 84 ms 80 ms cr1.cgcil.ip.att.net [12.122.18.21]

13 83 ms 81 ms 80 ms cr2.dvmco.ip.att.net [12.122.31.85]

14 86 ms 85 ms 83 ms cr1.slkut.ip.att.net [12.122.30.25]

15 88 ms 85 ms 83 ms cr2.la2ca.ip.att.net [12.122.30.30]

16 76 ms 73 ms 126 ms cr84.la2ca.ip.att.net [12.123.30.249]

17 * 90 ms 130 ms gar5.la2ca.ip.att.net [12.122.129.25]

18 128 ms 83 ms 116 ms 12.122.255.74

19 82 ms * 85 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]

20 12.129.211.34 reports: Destination net unreachable.



Trace complete.



Tracing route to 206.16.147.56 over a maximum of 30 hops



1 11 ms 7 ms 7 ms 10.206.216.1

2 204 ms 14 ms 12 ms static-216-36-30-225.cpe.metrocast.net [216.36.30.225]

3 20 ms 22 ms * static-216-36-30-202.cpe.metrocast.net [216.36.30.202]

4 28 ms 27 ms 26 ms static-216-36-30-201.cpe.metrocast.net [216.36.30.201]

5 143 ms 203 ms 170 ms border7.tge1-4.harron-3.wdc002.pnap.net [63.251.92.161]

6 38 ms 31 ms 31 ms core1.te5-1-bbnet1.wdc002.pnap.net [216.52.127.7]

7 35 ms 33 ms 31 ms ber1-ten-3-1.virginiaequinix.savvis.net [208.173.159.1]

8 36 ms 31 ms 33 ms er2-tengig-9-0-0.VirginiaEquinix.savvis.net [204.70.198.21]

9 37 ms 33 ms 33 ms 192.205.36.81

10 49 ms 46 ms 49 ms cr2.wswdc.ip.att.net [12.122.84.46]

11 * 79 ms 46 ms cr2.n54ny.ip.att.net [12.122.3.37]

12 95 ms 45 ms 45 ms cr1.cb1ma.ip.att.net [12.122.31.126]

13 58 ms 52 ms 49 ms gar5.cb1ma.ip.att.net [12.122.145.33]

14 46 ms 43 ms 43 ms 12-122-254-14.attens.net [12.122.254.14]

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * *
Reply Quote
85 Troll Druid
3775


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

over a maximum of 30 hops:



1 12 ms * 78 ms 10.206.216.1

2 9 ms 9 ms 7 ms static-216-36-30-225.cpe.metrocast.net [216.36.30.225]

3 14 ms 12 ms 13 ms static-216-36-30-202.cpe.metrocast.net [216.36.30.202]

4 24 ms 24 ms 23 ms static-216-36-30-201.cpe.metrocast.net [216.36.30.201]

5 20 ms 20 ms * border7.tge1-4.harron-3.wdc002.pnap.net [63.251.92.161]

6 11 ms 189 ms 13 ms core2.te5-2-bbnet2.wdc002.pnap.net [216.52.127.72]

7 14 ms 11 ms 10 ms TenGigE0-3-4-0.GW1.IAD8.ALTER.NET [152.179.50.53]

8 77 ms 63 ms 25 ms 0.xe-3-1-2.XL3.IAD8.ALTER.NET [152.63.35.146]

9 26 ms 12 ms 11 ms 0.ae3.BR1.IAD8.ALTER.NET [152.63.33.117]

10 11 ms 12 ms 11 ms 192.205.36.141

11 219 ms 206 ms 85 ms cr2.wswdc.ip.att.net [12.122.81.250]

12 193 ms 135 ms 265 ms cr1.cgcil.ip.att.net [12.122.18.21]

13 80 ms 79 ms 82 ms cr2.dvmco.ip.att.net [12.122.31.85]

14 87 ms 165 ms 201 ms cr1.slkut.ip.att.net [12.122.30.25]

15 172 ms 205 ms 86 ms cr2.la2ca.ip.att.net [12.122.30.30]

16 77 ms 128 ms 102 ms cr84.la2ca.ip.att.net [12.123.30.249]

17 188 ms 85 ms 85 ms gar5.la2ca.ip.att.net [12.122.129.25]

18 94 ms 85 ms 85 ms 12.122.255.74

19 94 ms 203 ms 83 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]

20 12.129.211.34 reports: Destination net unreachable.



Trace complete.
Reply Quote
MVP - Technical Support
100 Draenei Mage
7170
First off when you get bad latency you need to be doing traceroutes specifically to your realm server not the login server. The login server only governs whether you stay connected or not. Game data is sent to your realm server.

You can find the IP address for your realm server on :

http://www.wowpedia.org/US_Realm_List_By_Datacenter

Now I've had a look at what traceroutes you have posted.

You are consistently getting bad lag to your first hop. This would usually be your modem router.

Also it looks like your ISP is having issues when it hands off data to it's peer partners . Your ISP does not own all the internet and neither does AT & T. So at some point it's going to go through someone else's network.

These are peer partners. They handle getting data futher up the chain if it were. Unfortunately your not a customer of theirs , your ISP is.

So you need to get your ISP to raise a ticket with their peer partners.
________________________________________________
Bringing you walls of text and cookies since 2005 :)

Mac Tech Support MVP (moonlights in other forums)
Here to Help :)
Reply Quote
90 Troll Hunter
6335
1 12 ms * 78 ms 10.206.216.1


You also have issues before you even leave your home. Looks like a wireless connection (not supported) and you have packet loss and latency issues.
________________________________________________
Unofficial WoW Tech Support Pages
http://www.wowpedia.org/Portal:Technical_support
Live Support Chat
irc://chat.freenode.net/wowtech
http://webchat.freenode.net/?channels=wowtech
Reply Quote
85 Troll Druid
3775
I changed it to coilfang and ran two more. I'd love more input from you. I have a wireless network adapter I use to connect to my internet.. However I've been through two of them and about two months ago it was never an issue at all.

Tracing route to 199.107.25.9 over a maximum of 30 hops



1 11 ms 73 ms 13 ms 10.206.216.1

2 11 ms 36 ms 133 ms static-216-36-30-225.cpe.metrocast.net [216.36.30.225]

3 18 ms 146 ms 16 ms static-216-36-30-202.cpe.metrocast.net [216.36.30.202]

4 150 ms 36 ms 47 ms static-216-36-30-201.cpe.metrocast.net [216.36.30.201]

5 111 ms 11 ms 12 ms border7.tge1-4.harron-3.wdc002.pnap.net [63.251.92.161]

6 14 ms 60 ms 13 ms core2.te5-1-bbnet1.wdc002.pnap.net [216.52.127.8]

7 13 ms 13 ms 14 ms 12.90.32.9

8 19 ms 78 ms 22 ms cr2.wswdc.ip.att.net [12.123.10.138]

9 32 ms 22 ms 20 ms cr2.n54ny.ip.att.net [12.122.3.37]

10 23 ms 22 ms 20 ms cr84.n54ny.ip.att.net [12.122.115.94]

11 219 ms 26 ms 165 ms gar20.n54ny.ip.att.net [12.123.2.141]

12 25 ms 27 ms 38 ms 12-122-254-114.attens.net [12.122.254.114]

13 22 ms 21 ms 21 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

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.



Tracing route to 199.107.25.9 over a maximum of 30 hops



1 * 12 ms 11 ms 10.206.216.1

2 87 ms 9 ms 10 ms static-216-36-30-225.cpe.metrocast.net [216.36.30.225]

3 9 ms 16 ms 8 ms static-216-36-30-202.cpe.metrocast.net [216.36.30.202]

4 13 ms 62 ms 9 ms static-216-36-30-201.cpe.metrocast.net [216.36.30.201]

5 12 ms 13 ms 19 ms border7.tge1-4.harron-3.wdc002.pnap.net [63.251.92.161]

6 100 ms 22 ms 21 ms core2.te5-1-bbnet1.wdc002.pnap.net [216.52.127.8]

7 27 ms 26 ms 26 ms 12.90.32.9

8 35 ms 95 ms 37 ms cr2.wswdc.ip.att.net [12.123.10.138]

9 40 ms 41 ms 42 ms cr2.n54ny.ip.att.net [12.122.3.37]

10 40 ms 155 ms 44 ms cr84.n54ny.ip.att.net [12.122.115.94]

11 144 ms 42 ms 33 ms gar20.n54ny.ip.att.net [12.123.2.141]

12 39 ms 131 ms 37 ms 12-122-254-114.attens.net [12.122.254.114]

13 27 ms 31 ms 26 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

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.


Reply Quote
80 Blood Elf Priest
2865
When latency spikes in the midst of a tracert,it is usually due to ICMP depriortization. ICMP is reduced in priority by backhaul providers to allow pertinent information be expedited. The end result is where it counts, and due to the fact that Blizzard has ICMP disabled upon reaching their systems, we can only go by the hop prior to Battle.net. Based on the trace routes provided here, I wouldn't say that ATTENS was the cause of this situation.
Edited by Mireile on 3/27/2011 10:35 AM PDT
Reply Quote
90 Troll Hunter
6335
There are strict rules regarding ICMP according to RFC 792. Deprioritizing ICMP packets is not allowed, and I know of no ISP or backbone provider that does this.

OP. You will need to go to a hardwired connection in order to troubleshoot this correctly. You're having too many issues with the wireless connection.
________________________________________________
Unofficial WoW Tech Support Pages
http://www.wowpedia.org/Portal:Technical_support
Live Support Chat
irc://chat.freenode.net/wowtech
http://webchat.freenode.net/?channels=wowtech
Reply Quote
80 Blood Elf Priest
2865
There are strict rules regarding ICMP according to RFC 792. Deprioritizing ICMP packets is not allowed, and I know of no ISP or backbone provider that does this.

OP. You will need to go to a hardwired connection in order to troubleshoot this correctly. You're having too many issues with the wireless connection.
________________________________________________
Unofficial WoW Tech Support Pages
http://www.wowpedia.org/Portal:Technical_support
Live Support Chat
irc://chat.freenode.net/wowtech
http://webchat.freenode.net/?channels=wowtech


Several providers de-prioritize ICMP time-exceeded messages or rate-limit responses at the router level. Are you seriously denying this?
Edited by Mireile on 3/27/2011 11:09 AM PDT
Reply Quote
Support Forum Agent
1 12 ms * 78 ms 10.206.216.1

You also have issues before you even leave your home. Looks like a wireless connection (not supported) and you have packet loss and latency issues.


To echo what Drez is saying, your connection is so poor before it leaves your location that any other troubleshooting is mostly just speculation until you fix the situation with your home network. Your next step is to switch to a wired connection. Wireless connections are just radio waves and can be interfered with by numerable means. If your security is poor, your neighbors could even be leeching off of your connection. At any rate, switching to wired is required at this point for further troubleshooting. Good luck!


____________________________________________________________________________
If you think I'm being a helpful tech then let us know at- https://www.surveymk.com/s/R6YGTBT

Is your issue urgent? Need direct assistance? Contact an Accounts and Technical Services Rep! http://us.blizzard.com/en-us/company/about/contact.html

Good luck with the issue, and good gaming!
____________________________________________________________________________
Edited by Davidba on 3/27/2011 1:42 PM PDT
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)

Reported!

[Close]