If it feels like your WoW client just randomly stops getting updates or perhaps you're stuck trying to cast a spell and nothing happens for 5 seconds then see these links:
https://us.battle.net/support/en/article/looking-glass
https://us.battle.net/support/en/articl ... traceroute
https://us.battle.net/support/en/articl ... hping-test
The issue can be anywhere from your network equipment at home, to your ISP, or to congestion at ATT. For me at least, it seems to come up once in a while. It's really hard to catch, but this one time it's not Comcast's fault.
Diagnosing WoW connection issues (for Lilli!)
Re: Diagnosing WoW connection issues (for Lilli!)
Look, I did the pathping test so far. Um....? Nodes? What the heck is a node? Who can read this? 100% mess up in #7?
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 HP-DC7800.hsd1.nh.comcast.net. [10.0.0.12]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 96.120.66.237
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% GE-9-41-rr01.whartford.ct.hartford.comcast.net [68.87.181.117]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% be-31-ar01.needham.ma.boston.comcast.net [68.85.106.93]
0/ 100 = 0% |
5 20ms 0/ 100 = 0% 0/ 100 = 0% be-7015-cr01.newyork.ny.ibone.comcast.net [68.86.90.217]
0/ 100 = 0% |
6 19ms 0/ 100 = 0% 0/ 100 = 0% c-eth-0-2-0-pe04.111eighthave.ny.ibone.comcast.net [68.86.87.98]
0/ 100 = 0% |
7 22ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.33
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.n54ny.ip.att.net [12.122.131.86]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.1.2]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12.122.95.109
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 HP-DC7800.hsd1.nh.comcast.net. [10.0.0.12]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 96.120.66.237
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% GE-9-41-rr01.whartford.ct.hartford.comcast.net [68.87.181.117]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% be-31-ar01.needham.ma.boston.comcast.net [68.85.106.93]
0/ 100 = 0% |
5 20ms 0/ 100 = 0% 0/ 100 = 0% be-7015-cr01.newyork.ny.ibone.comcast.net [68.86.90.217]
0/ 100 = 0% |
6 19ms 0/ 100 = 0% 0/ 100 = 0% c-eth-0-2-0-pe04.111eighthave.ny.ibone.comcast.net [68.86.87.98]
0/ 100 = 0% |
7 22ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.33
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.n54ny.ip.att.net [12.122.131.86]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.1.2]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12.122.95.109
Re: Diagnosing WoW connection issues (for Lilli!)
I'm just gonna post this all here and see if someone has a suggestion for computer illiterate me.... WTF is this crap? That's a lot of **** and time outs!
Tracing route to 12.129.209.68 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 10.0.0.1
2 8 ms 10 ms 9 ms 96.120.66.237
3 9 ms 9 ms 10 ms GE-9-41-rr01.whartford.ct.hartford.comcast.net [68.87.181.117]
4 18 ms 15 ms 11 ms be-31-ar01.needham.ma.boston.comcast.net [68.85.106.93]
5 22 ms 21 ms 20 ms be-7015-cr01.newyork.ny.ibone.comcast.net [68.86.90.217]
6 19 ms 19 ms 24 ms c-eth-0-2-0-pe04.111eighthave.ny.ibone.comcast.net [68.86.87.98]
7 26 ms 31 ms 27 ms 192.205.37.33
8 42 ms 49 ms 41 ms cr1.n54ny.ip.att.net [12.122.131.86]
9 46 ms 41 ms 43 ms cr2.cgcil.ip.att.net [12.122.1.2]
10 54 ms 39 ms 38 ms 12.122.95.109
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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 12.129.209.68 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 10.0.0.1
2 8 ms 10 ms 9 ms 96.120.66.237
3 9 ms 9 ms 10 ms GE-9-41-rr01.whartford.ct.hartford.comcast.net [68.87.181.117]
4 18 ms 15 ms 11 ms be-31-ar01.needham.ma.boston.comcast.net [68.85.106.93]
5 22 ms 21 ms 20 ms be-7015-cr01.newyork.ny.ibone.comcast.net [68.86.90.217]
6 19 ms 19 ms 24 ms c-eth-0-2-0-pe04.111eighthave.ny.ibone.comcast.net [68.86.87.98]
7 26 ms 31 ms 27 ms 192.205.37.33
8 42 ms 49 ms 41 ms cr1.n54ny.ip.att.net [12.122.131.86]
9 46 ms 41 ms 43 ms cr2.cgcil.ip.att.net [12.122.1.2]
10 54 ms 39 ms 38 ms 12.122.95.109
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.
Re: Diagnosing WoW connection issues (for Lilli!)
Looking glass thingie? So confusing!
PING 75.68.97.233 (75.68.97.233) 56(84) bytes of data.
64 bytes from 75.68.97.233: icmp_seq=1 ttl=51 time=40.4 ms
64 bytes from 75.68.97.233: icmp_seq=2 ttl=51 time=40.6 ms
64 bytes from 75.68.97.233: icmp_seq=3 ttl=51 time=39.6 ms
64 bytes from 75.68.97.233: icmp_seq=4 ttl=51 time=40.4 ms
--- 75.68.97.233 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3039ms
rtt min/avg/max/mdev = 39.626/40.281/40.660/0.461 ms
traceroute to 75.68.97.233 (75.68.97.233), 15 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
traceroute to 75.68.97.233 (75.68.97.233), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.441 ms 0.561 ms 0.676 ms
2 * * *
3 206.18.96.213 (206.18.96.213) 0.384 ms 0.455 ms 0.522 ms
4 63.240.130.189 (63.240.130.189) 0.505 ms 0.595 ms 0.675 ms
5 12.122.251.13 (12.122.251.13) 1.922 ms 1.934 ms 1.945 ms
6 cr2.cgcil.ip.att.net (12.122.132.242) 3.567 ms 3.208 ms 2.588 ms
7 cgr1.cgcil.ip.att.net (12.122.132.157) 5.253 ms 5.257 ms 5.257 ms
8 192.205.37.22 (192.205.37.22) 3.928 ms 4.154 ms 4.223 ms
9 he-3-3-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.83.161) 2.469 ms he-2-6-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.87.129) 3.294 ms he-2-5-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.87.125) 5.759 ms
10 be-7922-ar01.woburn.ma.boston.comcast.net (68.86.91.6) 30.239 ms 32.690 ms 32.665 ms
11 te-0-0-0-0-sur01.londonderry.nh.boston.comcast.net (68.85.106.90) 33.174 ms 33.177 ms 35.032 ms
12 68.87.158.222 (68.87.158.222) 31.513 ms 31.483 ms 31.447 ms
13 c-75-68-97-233.hsd1.nh.comcast.net (75.68.97.233) 41.020 ms 41.004 ms 41.008 ms
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.5 0.4 0.5 0.0
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 206.18.96.213 0.0% 10 0.3 0.3 0.3 0.7 0.1
4. 63.240.130.189 0.0% 10 0.4 6.4 0.4 60.5 19.0
5. 12.122.251.13 0.0% 10 2.0 8.2 1.9 52.8 16.1
6. cr2.cgcil.ip.att.net 0.0% 10 4.7 5.0 3.3 6.2 0.9
7. cgr1.cgcil.ip.att.net 0.0% 10 3.8 4.3 2.8 6.1 1.3
8. 192.205.37.22 0.0% 10 4.3 3.0 2.6 4.3 0.5
9. he-3-3-0-0-cr01.350ecermak.il.ibone.comcast.net 0.0% 10 2.8 4.5 2.8 6.2 1.4
10. be-7922-ar01.woburn.ma.boston.comcast.net 0.0% 10 34.3 32.0 30.3 34.3 1.4
11. te-0-0-0-0-sur01.londonderry.nh.boston.comcast.net 0.0% 10 35.9 34.6 33.1 35.9 1.0
12. 68.87.158.222 0.0% 10 31.5 31.5 31.5 31.5 0.0
13. c-75-68-97-233.hsd1.nh.comcast.net 0.0% 10 49.5 40.9 39.1 49.5 3.1
PING 75.68.97.233 (75.68.97.233) 56(84) bytes of data.
64 bytes from 75.68.97.233: icmp_seq=1 ttl=51 time=40.4 ms
64 bytes from 75.68.97.233: icmp_seq=2 ttl=51 time=40.6 ms
64 bytes from 75.68.97.233: icmp_seq=3 ttl=51 time=39.6 ms
64 bytes from 75.68.97.233: icmp_seq=4 ttl=51 time=40.4 ms
--- 75.68.97.233 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3039ms
rtt min/avg/max/mdev = 39.626/40.281/40.660/0.461 ms
traceroute to 75.68.97.233 (75.68.97.233), 15 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
traceroute to 75.68.97.233 (75.68.97.233), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.441 ms 0.561 ms 0.676 ms
2 * * *
3 206.18.96.213 (206.18.96.213) 0.384 ms 0.455 ms 0.522 ms
4 63.240.130.189 (63.240.130.189) 0.505 ms 0.595 ms 0.675 ms
5 12.122.251.13 (12.122.251.13) 1.922 ms 1.934 ms 1.945 ms
6 cr2.cgcil.ip.att.net (12.122.132.242) 3.567 ms 3.208 ms 2.588 ms
7 cgr1.cgcil.ip.att.net (12.122.132.157) 5.253 ms 5.257 ms 5.257 ms
8 192.205.37.22 (192.205.37.22) 3.928 ms 4.154 ms 4.223 ms
9 he-3-3-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.83.161) 2.469 ms he-2-6-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.87.129) 3.294 ms he-2-5-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.87.125) 5.759 ms
10 be-7922-ar01.woburn.ma.boston.comcast.net (68.86.91.6) 30.239 ms 32.690 ms 32.665 ms
11 te-0-0-0-0-sur01.londonderry.nh.boston.comcast.net (68.85.106.90) 33.174 ms 33.177 ms 35.032 ms
12 68.87.158.222 (68.87.158.222) 31.513 ms 31.483 ms 31.447 ms
13 c-75-68-97-233.hsd1.nh.comcast.net (75.68.97.233) 41.020 ms 41.004 ms 41.008 ms
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.5 0.4 0.5 0.0
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 206.18.96.213 0.0% 10 0.3 0.3 0.3 0.7 0.1
4. 63.240.130.189 0.0% 10 0.4 6.4 0.4 60.5 19.0
5. 12.122.251.13 0.0% 10 2.0 8.2 1.9 52.8 16.1
6. cr2.cgcil.ip.att.net 0.0% 10 4.7 5.0 3.3 6.2 0.9
7. cgr1.cgcil.ip.att.net 0.0% 10 3.8 4.3 2.8 6.1 1.3
8. 192.205.37.22 0.0% 10 4.3 3.0 2.6 4.3 0.5
9. he-3-3-0-0-cr01.350ecermak.il.ibone.comcast.net 0.0% 10 2.8 4.5 2.8 6.2 1.4
10. be-7922-ar01.woburn.ma.boston.comcast.net 0.0% 10 34.3 32.0 30.3 34.3 1.4
11. te-0-0-0-0-sur01.londonderry.nh.boston.comcast.net 0.0% 10 35.9 34.6 33.1 35.9 1.0
12. 68.87.158.222 0.0% 10 31.5 31.5 31.5 31.5 0.0
13. c-75-68-97-233.hsd1.nh.comcast.net 0.0% 10 49.5 40.9 39.1 49.5 3.1
Re: Diagnosing WoW connection issues (for Lilli!)
Hey Lilli, are you on WiFi?
I actually think the IP is wrong in that article. TN is in the Chicago data center and not Los Angeles, so it should be 63.240.161.189 instead (as per http://wow.gamepedia.com/Americas_regio ... datacenter).
I actually think the IP is wrong in that article. TN is in the Chicago data center and not Los Angeles, so it should be 63.240.161.189 instead (as per http://wow.gamepedia.com/Americas_regio ... datacenter).
Re: Diagnosing WoW connection issues (for Lilli!)
Yes, wifi. So should I be using that 62 number for my ping test thingie?
Re: Diagnosing WoW connection issues (for Lilli!)
Yeah, that's right. There's also this new thread on the Blizz tech forums that you might want to post in (2/5 - Comcast Connection/Latency Issues): http://us.battle.net/wow/en/forum/topic/16202231154
edit. I should probably as well but I need to wait till the issue pops up again.
edit. I should probably as well but I need to wait till the issue pops up again.