Loading Profile...
warcraft latency Issue returns for May 2k9
Having extremely high latency playing World of Warcraft. Latency ranges from 300 to over 2000 ms. Connection to any other service is fine. Pings to yahoo resolve in less than 60 ms, with no packet loss. Running trace routes to server shows issue begins at
cr1.cgcil.ip.att.net [12.122.133.138]
cr2.dvmco.ip.att.net [12.122.31.85]
cr1.slkut.ip.att.net [12.122.30.25]
cr2.la2ca.ip.att.net [12.122.30.30]
gar5.la2ca.ip.att.net [12.122.129.25]
I have run several trace route tests. All times double or triple once I reach these nodes. I do not believe this is a single line issue, because comcast customer's across the nation are reporting the exact same results. For example: http://forums.worldofwarcraft.com/thr...
I have not found a similar issue with any of the other ISP's.
What is being done about this comcast?
cr1.cgcil.ip.att.net [12.122.133.138]
cr2.dvmco.ip.att.net [12.122.31.85]
cr1.slkut.ip.att.net [12.122.30.25]
cr2.la2ca.ip.att.net [12.122.30.30]
gar5.la2ca.ip.att.net [12.122.129.25]
I have run several trace route tests. All times double or triple once I reach these nodes. I do not believe this is a single line issue, because comcast customer's across the nation are reporting the exact same results. For example: http://forums.worldofwarcraft.com/thr...
I have not found a similar issue with any of the other ISP's.
What is being done about this comcast?
I’m ticked off and tired of dealing with it.
36
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Here is mine:
Tracing route to 206.17.111.41 over a maximum of 30 hops
1 6 ms 6 ms 11 ms 73.98.176.1
2 8 ms 7 ms 8 ms 68.87.205.225
3 7 ms 7 ms 8 ms te-0-9-0-0-ar01.burien.wa.seattle.comcast.net [68.86.96.129]
4 11 ms 15 ms 11 ms pos-0-6-0-0-cr01.portland.or.ibone.comcast.net [68.86.90.221]
5 25 ms 23 ms 23 ms pos-1-14-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.201]
6 26 ms 27 ms 25 ms pos-0-8-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.78]
7 27 ms 27 ms 27 ms er1-tengig3-4.sanjoseequinix.savvis.net [208.173.53.137]
8 28 ms 28 ms 27 ms pr2-ge-2-0-0.SanJoseEquinix.savvis.net [204.70.200.130]
9 28 ms 30 ms 29 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
10 103 ms 104 ms 108 ms cr1.sffca.ip.att.net [12.122.137.126]
11 100 ms 102 ms 100 ms cr1.cgcil.ip.att.net [12.122.4.122]
12 124 ms 104 ms * cr2.cgcil.ip.att.net [12.122.2.54]
13 * 103 ms 105 ms cr1.n54ny.ip.att.net [12.122.1.1]
14 99 ms 99 ms 100 ms cr2.n54ny.ip.att.net [12.122.2.14]
15 107 ms 105 ms * cr1.cb1ma.ip.att.net [12.122.31.126]
16 99 ms 98 ms 97 ms gar5.cb1ma.ip.att.net [12.122.145.29]
17 99 ms 100 ms 100 ms 12-122-254-14.attens.net [12.122.254.14]
18 100 ms 102 ms 101 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]
30 * * * Request timed out.
Trace complete. -
Inappropriate?I also have this exact same problem while trying to play world of warcraft!!! Please do something Comcast! This just started 2 nights ago. I have never had problems like this previously.
-
Inappropriate?Game is unplayable. At $15/month for WoW and $50/month for 16Mbps service (upgraded because of WoW), I'm tossing alot of money into the wind.
I’m frustrated and annoyed.
-
-
Inappropriate?I'm also having this problem. Started during Memorial Day weekend. Pings average about 600 in World of Warcraft and is fine for everything else. In Team Fortress 2 I can play on servers with 20-30 ping.
This really needs to be looked into. From talking to other people in WoW, many many Comcast customers are having this issue. -
Inappropriate?This is a real problem for me since the only reason I use this computer for is World of Warcraft. Other ISP's do not have this problem. If this problem persist without me getting some answers, I will be switching ISP's.
Official Blizzard Tech Support Quote:
"We are aware of a route related issue that has affected a number of people playing world of Warcraft.
We have been in contact with out ISP and they have been on contact with the other ISPs involved.
Blizzard does not have any ability to address route related issues beyond this.
I recommend continuing to contact your ISPs and ask for them to investigate as well.
If they are not able to ask for tier 2 or 3 technicians. Try to get ticket or reference numbers in case you need to make multiple calls.
ISPs are responsible for the routing of packets online. If issues occur outside of their network they may need to contact their peering or transit partners in order to provide a proper connection."
"If an issue occurs on the route there is nothing we can do beyond contact our ISP and have them contact the other ISPs involved.
This is the same recourse the end user has.
There is no way for our network technicians to do anything on the route just as there is no way for you to. The routes are maintained by the ISPs, the routing is determined by the ISPs.
We are monitoring the situation but have done what we can to address the issue. My suggestion to people is that they do what they can as well. Believe it our not, the end users have as strong a voice as we do when dealing with the ISPs and often the best results come when reports are made form both sides.
We have a louder voice but it is only one voice and there is strength in numbers."
3d tracerts:
http://i144.photobucket.com/albums/r1...
http://i144.photobucket.com/albums/r1...
Netstat:
C:\Users\Steveo>netstat
Active Connections
Proto Local Address Foreign Address State
TCP 76.112.184.247:49398 a96-17-76-161:http CLOSE_WAIT
TCP 76.112.184.247:51529 206.17.111.31:3724 ESTABLISHED
2nd on the list is the blizzard game server.
CMD tracert to blizzard server:
C:\Users\Steveo>tracert 206.17.111.31
Tracing route to 206.17.111.31 over a maximum of 30 hops
1 * * * Request timed out.
2 16 ms 14 ms 7 ms ge-1-13ur02.vanburen.mi.michigan.comcast.net[68.85.218.237]
3 7 ms 9 ms 10 ms te-0-6-0-4-ar01.taylor.mi.michigan.comcast.net [
68.87.190.41]
4 12 ms 13 ms 14 ms pos-0-5-0-0-cr01.cleveland.oh.ibone.comcast.net
[68.86.90.105]
5 23 ms 22 ms 23 ms pos-0-8-0-0-cr01.chicago.il.ibone.comcast.net [6
8.86.85.50]
6 22 ms 23 ms 24 ms 68.86.86.78
7 24 ms 24 ms 27 ms ber1-tengig3-4.chicagoequinix.savvis.net [208.17
3.180.45]
8 39 ms 29 ms 30 ms ber2-te-3-4.chicagoequinix.savvis.net [204.70.19
8.78]
9 31 ms * 31 ms savvis-gw.cgcil.ip.att.net [192.205.35.41]
10 54 ms 54 ms 53 ms cr2.cgcil.ip.att.net [12.122.132.142]
11 58 ms 59 ms 59 ms cr1.n54ny.ip.att.net [12.122.1.1]
12 61 ms 59 ms 58 ms cr2.n54ny.ip.att.net [12.122.2.14]
13 58 ms 58 ms 58 ms cr1.cb1ma.ip.att.net [12.122.31.126]
14 * 70 ms 59 ms gar5.cb1ma.ip.att.net [12.122.145.33]
15 58 ms 60 ms 58 ms 12-122-254-14.attens.net [12.122.254.14]
16 56 ms 59 ms 56 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.13
0.0.170]
17 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
I’m Very frustrated
-
Inappropriate?The husband and I are also having similar problems which started around 5/23/09. WoW is pretty much unplayable during peak hours. I am one our guild's main tanks so the lag and the d/c's make raiding pretty much impossible.
Tracing route to 206.17.111.29 over a maximum of 30 hops
1 <1><1><1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 7 ms 8 ms ge-1-39-ur01.muncie.in.indiana.comcast.net [68.86.185.33]
4 10 ms 8 ms 9 ms be-20-ar01.indianapolis.in.indiana.comcast.net [68.86.187.142]
5 15 ms 14 ms 14 ms pos-0-15-0-0-ar01.area4.il.chicago.comcast.net [68.87.230.9]
6 15 ms 14 ms 16 ms pos-1-13-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.49]
7 15 ms 16 ms 15 ms pos-0-1-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.38]
8 35 ms 25 ms 34 ms ber1-tengig3-3.chicagoequinix.savvis.net [208.173.180.41]
9 29 ms 25 ms 21 ms ber2-te-3-4.chicagoequinix.savvis.net [204.70.198.78]
10 22 ms * 21 ms savvis-gw.cgcil.ip.att.net [192.205.35.41]
11 51 ms 51 ms 50 ms cr2.cgcil.ip.att.net [12.122.132.138]
12 51 ms 50 ms 49 ms cr1.n54ny.ip.att.net [12.122.1.1]
13 51 ms 48 ms 46 ms cr2.n54ny.ip.att.net [12.122.2.14]
14 46 ms 45 ms 45 ms cr1.cb1ma.ip.att.net [12.122.31.126]
15 45 ms 45 ms 45 ms gar5.cb1ma.ip.att.net [12.122.145.29]
16 46 ms 45 ms 48 ms 12-122-254-14.attens.net [12.122.254.14]
17 50 ms 50 ms 50 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.130.0.170]
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.
I’m very frustrated
-
Inappropriate?Same issue here. Problems began for me on Saturday, May 23.
Location: Howell, MI
Traceroute to WoW Server:
TraceRoute to 206.17.111.18
Hop (ms) (ms) (ms) IP Address Host name
1 23 13 25 72.249.134.177 -
2 7 15 9 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
3 14 12 11 4.68.19.204 ae-4-99.edge2.dallas3.level3.net
4 17 11 10 192.205.35.221 -
5 82 81 65 12.122.138.22 cr2.dlstx.ip.att.net
6 94 84 60 12.122.28.173 cr1.attga.ip.att.net
7 72 71 67 12.122.1.174 cr2.wswdc.ip.att.net
8 65 59 55 12.122.3.37 cr2.n54ny.ip.att.net
9 67 64 63 12.122.31.126 cr1.cb1ma.ip.att.net
10 79 61 55 12.122.145.33 gar5.cb1ma.ip.att.net
11 63 56 59 12.122.254.14 12-122-254-14.attens.net
12 72 67 58 12.130.0.174 mdf001c7613r0004-gig-12-1.bos1.attens.net
13 Timed out Timed out Timed out -
14 Timed out Timed out Timed out -
15 Timed out Timed out Timed out -
16 Timed out Timed out Timed out -
Trace aborted
I’m bored with this issue.....
-
Inappropriate?I am also experiencing this issue. I connect to blizzard's Boston data center from a city bordering Boston.
I've been experiencing frequent disconnections and large latency spiking since May 24.
Here is a traceroute from this afternoon while the problem was evident.
Tracing route to 206.17.111.123 over a maximum of 30 hops
1 7 ms 8 ms 7 ms 73.195.4.1
2 7 ms 7 ms 7 ms 68.85.141.241
3 8 ms 7 ms 7 ms po-51-ur02.lynn.ma.boston.comcast.net [68.87.147.90]
4 9 ms 11 ms 9 ms be-52-crs01.needham.ma.boston.comcast.net [68.87.162.149]
5 12 ms 13 ms 13 ms pos-0-0-0-0-ar99.chartford.ct.hartford.comcast.net [68.85.162.70]
6 44 ms 21 ms 17 ms pos-2-4-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.61]
7 16 ms 16 ms 15 ms pos-0-1-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.86.46]
8 18 ms 17 ms 17 ms er2-tengig3-3.newyork.savvis.net [208.173.138.13]
9 43 ms 43 ms 44 ms 192.205.35.9
10 52 ms 49 ms 49 ms cr2.n54ny.ip.att.net [12.122.130.102]
11 49 ms 49 ms 49 ms cr1.cb1ma.ip.att.net [12.122.31.126]
12 48 ms 49 ms 48 ms gar5.cb1ma.ip.att.net [12.122.145.29]
13 49 ms 47 ms * 12-122-254-14.attens.net [12.122.254.14]
14 49 ms 58 ms 45 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.130.0.170]
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. -
Inappropriate?I also have this same issue and it also began this past week.
I live in Needham, MA and have Comcast as my ISP.
Here is my latest tracer route:
Comcast ISP
Needham, MA
Duskwood realm
Still having same connection issues. This is my latest and most current tracer info:
Tracing route to 206.17.111.31 over a maximum of 30 hops
1 1 ms 1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms c-3-0-ubr02.milford.ma.boston.comcast.net [73.171.0.1]
3 9 ms 8 ms 8 ms ge-3-29-ur01.needham.ma.boston.comcast.net [68.85.161.137]
4 8 ms 7 ms 7 ms te-0-5-0-4-crs01.needham.ma.boston.comcast.net [68.87.145.161]
5 11 ms 10 ms 11 ms pos-0-1-0-0-ar99.chartford.ct.hartford.comcast.net [68.85.162.74]
6 14 ms 14 ms 14 ms pos-2-3-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.57]
7 15 ms 14 ms 13 ms pos-0-1-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.86.46]
8 15 ms 15 ms 14 ms er2-tengig3-3.newyork.savvis.net [208.173.138.13]
9 38 ms 38 ms 38 ms 192.205.35.9
10 44 ms 42 ms 48 ms cr2.n54ny.ip.att.net [12.122.130.106]
11 43 ms 45 ms 46 ms cr1.cb1ma.ip.att.net [12.122.31.126]
12 43 ms 42 ms 44 ms gar5.cb1ma.ip.att.net [12.122.145.33]
13 105 ms 45 ms 47 ms 12-122-254-14.attens.net [12.122.254.14]
14 45 ms 45 ms 49 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]
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.
I’m confused
-
Inappropriate?Tracing route to 12.129.232.115 over a maximum of 30 hops
1 1 ms <1><1 ms 192.168.1.1]
2 13 ms 14 ms 34 ms te-4-1-ur09.sanjose.ca.sfba.comcast.net [68.85.190.169]
3 17 ms 11 ms 14 ms te-8-3-ur04.sanjose.ca.sfba.comcast.net [68.87.226.62]
4 27 ms 34 ms 13 ms te-7-1-ur03.sanjose.ca.sfba.comcast.net [68.87.192.41]
5 18 ms 37 ms 17 ms be-40-ar01.sfsutro.ca.sfba.comcast.net [68.87.226.225]
6 20 ms 30 ms 17 ms pos-1-7-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.90.153]
7 18 ms 19 ms 34 ms er1-tengig3-4.sanjoseequinix.savvis.net [208.173.53.137]
8 45 ms 19 ms 24 ms pr2-ge-2-0-0.SanJoseEquinix.savvis.net [204.70.200.130]
9 34 ms 19 ms 28 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
10 41 ms 34 ms 42 ms cr1.sffca.ip.att.net [12.122.137.126]
11 66 ms 47 ms 27 ms cr1.la2ca.ip.att.net [12.122.3.122]
12 33 ms 29 ms 25 ms gar5.la2ca.ip.att.net [12.122.128.25]
13 38 ms 29 ms 43 ms 12.122.255.74
14 27 ms 29 ms 97 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
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. -
Inappropriate?Current tracer route as of 6:51 PM, Wednesday May 27th:
Current tracer route
Comcast ISP
Needham, MA
Duskwood realm
Tracing route to 206.17.111.31 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 11 ms c-3-0-ubr02.milford.ma.boston.comcast.net [73.171.0.1]
3 6 ms 7 ms 8 ms ge-3-29-ur01.needham.ma.boston.comcast.net [68.85.161.137]
4 8 ms 8 ms 8 ms te-0-5-0-4-crs01.needham.ma.boston.comcast.net [68.87.145.161]
5 11 ms 11 ms 10 ms pos-0-1-0-0-ar99.chartford.ct.hartford.comcast.net [68.85.162.74]
6 13 ms 15 ms 15 ms pos-2-3-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.57]
7 14 ms 14 ms 15 ms pos-0-1-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.86.46]
8 18 ms 20 ms 15 ms er2-tengig3-3.newyork.savvis.net [208.173.138.13]
9 39 ms 42 ms 44 ms 192.205.35.9
10 48 ms 48 ms 48 ms cr2.n54ny.ip.att.net [12.122.130.106]
11 * 48 ms 48 ms cr1.cb1ma.ip.att.net [12.122.31.126]
12 * * 48 ms gar5.cb1ma.ip.att.net [12.122.145.33]
13 50 ms 50 ms 49 ms 12-122-254-14.attens.net [12.122.254.14]
14 * 51 ms 48 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 -
Inappropriate?Tracing route to 206.16.147.100 over a maximum of 30 hops
1 1 ms <1><1 ms 192.168.0.1
2 * * * Request timed out.
3 7 ms 7 ms 7 ms 68.85.141.57
4 8 ms 7 ms 7 ms te-9-1-ur02.derry.nh.boston.comcast.net [68.87.145.85]
5 7 ms 7 ms 7 ms te-8-2-ur01.lawrence.ma.boston.comcast.net [68.87.144.149]
6 9 ms 7 ms 7 ms po-21-ur02.lowell.ma.boston.comcast.net [68.87.144.146]
7 7 ms 7 ms 9 ms po-20-ur01.lowell.ma.boston.comcast.net [68.87.144.153]
8 11 ms 10 ms 10 ms be-21-crs01.needham.ma.boston.comcast.net [68.87.144.157]
9 14 ms 14 ms 16 ms pos-0-1-0-0-ar99.chartford.ct.hartford.comcast.net [68.85.162.74]
10 16 ms 15 ms 15 ms pos-2-3-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.57]
11 16 ms 17 ms 20 ms 68.86.86.74
12 17 ms 15 ms 15 ms er2-tengig3-4.newyork.savvis.net [208.173.138.17]
13 39 ms 38 ms 40 ms 192.205.35.9
14 46 ms 44 ms 46 ms cr2.n54ny.ip.att.net [12.122.130.106]
15 44 ms 45 ms 45 ms cr1.cb1ma.ip.att.net [12.122.31.126]
16 45 ms 45 ms 45 ms gar5.cb1ma.ip.att.net [12.122.145.29]
17 45 ms 45 ms 46 ms 12-122-254-14.attens.net [12.122.254.14]
18 47 ms 45 ms 45 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.130.0.170]
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. -
Inappropriate?I have had the same issue for the last 4 days with latency and lag spikes.
from seattle to a server in boston
have not had any trouble with conection untill 4 days ago.
something is broken plz fix it.
I’m frustrated
-
Inappropriate?Also having this problem.....
>tracert 206.17.111.32
racing route to 206.17.111.32 over a maximum of 30 hops
1 2 ms 1 ms 1 ms 192.168.1.1
2 11 ms 11 ms 8 ms 73.250.200.1
3 8 ms 7 ms 11 ms ge-3-43-ur02.danbury.ct.hartford.comcast.net [68
85.163.37]
4 12 ms 6 ms 9 ms te-8-3-ur01.danbury.ct.hartford.comcast.net [68.
6.231.225]
5 10 ms 13 ms 10 ms 68.85.162.185
6 13 ms 12 ms 13 ms be-10-ar99.chartford.ct.hartford.comcast.net [68
87.146.29]
7 18 ms 15 ms 14 ms pos-2-5-0-0-cr01.newyork.ny.ibone.comcast.net [6
.86.90.65]
8 17 ms 16 ms 14 ms 68.86.86.74
9 16 ms 19 ms 18 ms er2-tengig3-3.newyork.savvis.net [208.173.138.13
10 53 ms 46 ms 46 ms 192.205.35.9
11 101 ms 52 ms 52 ms cr2.n54ny.ip.att.net [12.122.130.106]
12 52 ms 48 ms 50 ms cr1.cb1ma.ip.att.net [12.122.31.126]
13 55 ms 53 ms 60 ms gar5.cb1ma.ip.att.net [12.122.145.33]
14 52 ms 55 ms 54 ms 12-122-254-14.attens.net [12.122.254.14]
15 64 ms 50 ms 56 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.13
.0.174]
16 * * * Request timed out.
17 -
Inappropriate?Tracing route to 206.16.147.46 over a maximum of 30 hops
1 <1><1><1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 14 ms 8 ms 68.86.113.33
4 9 ms 10 ms 10 ms be-50-ar01.burien.wa.seattle.comcast.net [68.86.
96.213]
5 13 ms 17 ms 13 ms pos-0-7-0-0-cr01.portland.or.ibone.comcast.net [
68.86.90.217]
6 29 ms 29 ms 27 ms pos-1-15-0-0-cr01.sacramento.ca.ibone.comcast.ne
t [68.86.85.197]
7 39 ms 29 ms 32 ms pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.85.181]
8 31 ms 30 ms 29 ms er1-tengig3-4.sanjoseequinix.savvis.net [208.173
.53.137]
9 29 ms 30 ms 30 ms pr2-ge-2-0-0.SanJoseEquinix.savvis.net [204.70.2
00.130]
10 33 ms 31 ms 31 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
11 106 ms 105 ms 109 ms cr1.sffca.ip.att.net [12.122.137.126]
12 100 ms 106 ms 101 ms cr1.cgcil.ip.att.net [12.122.4.122]
13 102 ms 102 ms 102 ms cr2.cgcil.ip.att.net [12.122.2.54]
14 101 ms 101 ms 101 ms cr1.n54ny.ip.att.net [12.122.1.1]
15 105 ms * 109 ms cr2.n54ny.ip.att.net [12.122.2.14]
16 106 ms 104 ms 105 ms cr1.cb1ma.ip.att.net [12.122.31.126]
17 104 ms 106 ms 105 ms gar5.cb1ma.ip.att.net [12.122.145.29]
18 102 ms 112 ms 101 ms 12-122-254-14.attens.net [12.122.254.14]
19 101 ms 101 ms 100 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.13
0.0.170]
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.
I’m frustrated
-
Inappropriate?Tracing route to us.logon.worldofwarcraft.com [12.129.232.115]
over a maximum of 30 hops:
1 1 ms <1><1 ms 192.168.1.1
2 8 ms 7 ms 8 ms 96.128.0.1
3 7 ms 7 ms 7 ms ge-2-2-ur01.rehoboth.ma.boston.comcast.net [68.85.160.173]
4 8 ms 8 ms 8 ms po-52-ar01.foxboro.ma.boston.comcast.net [68.87.144.117]
5 11 ms 10 ms 9 ms be-56-crs01.needham.ma.boston.comcast.net [68.85.162.181]
6 15 ms 15 ms 13 ms pos-0-0-0-0-ar99.chartford.ct.hartford.comcast.net [68.85.162.70]
7 17 ms 17 ms 24 ms pos-2-4-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.61]
8 17 ms 20 ms 16 ms 68.86.86.74
9 17 ms 17 ms 16 ms er2-tengig3-3.newyork.savvis.net [208.173.138.13]
10 45 ms 45 ms 45 ms 192.205.35.9
11 91 ms 89 ms 90 ms cr1.n54ny.ip.att.net [12.122.131.94]
12 90 ms 89 ms 89 ms cr2.cgcil.ip.att.net [12.122.1.2]
13 90 ms 91 ms 89 ms cr1.cgcil.ip.att.net [12.122.2.53]
14 88 ms 89 ms 88 ms cr2.dvmco.ip.att.net [12.122.31.85]
15 97 ms 90 ms 89 ms cr1.slkut.ip.att.net [12.122.30.25]
16 90 ms 90 ms 88 ms cr2.la2ca.ip.att.net [12.122.30.30]
17 88 ms 89 ms 88 ms gar5.la2ca.ip.att.net [12.122.129.25]
18 89 ms 89 ms 89 ms 12.122.255.74
19 90 ms 92 ms 89 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
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. -
Inappropriate?I am also having this problem. It started on May 25th. Here is my trace:
Tracing route to 206.17.111.121 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 18 ms 10 ms 8 ms 68.85.144.65
4 9 ms 13 ms 18 ms be-60-ar01.burien.wa.seattle.comcast.net [68.85.
240.85]
5 14 ms 13 ms 14 ms pos-0-6-0-0-cr01.portland.or.ibone.comcast.net [
68.86.90.221]
6 26 ms 26 ms 29 ms pos-1-13-0-0-cr01.sacramento.ca.ibone.comcast.ne
t [68.86.85.162]
7 38 ms 29 ms 37 ms pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.85.181]
8 30 ms 29 ms 31 ms er1-tengig3-4.sanjoseequinix.savvis.net [208.173
.53.137]
9 29 ms 29 ms 28 ms pr2-ge-2-0-0.SanJoseEquinix.savvis.net [204.70.2
00.130]
10 40 ms 34 ms 31 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
11 106 ms 108 ms 107 ms cr1.sffca.ip.att.net [12.122.137.126]
12 102 ms 105 ms 102 ms cr1.cgcil.ip.att.net [12.122.4.122]
13 107 ms 107 ms * cr2.cgcil.ip.att.net [12.122.2.54]
14 106 ms 106 ms 106 ms cr1.n54ny.ip.att.net [12.122.1.1]
15 101 ms 103 ms 100 ms cr2.n54ny.ip.att.net [12.122.2.14]
16 103 ms 102 ms 102 ms cr1.cb1ma.ip.att.net [12.122.31.126]
17 111 ms 107 ms 116 ms gar5.cb1ma.ip.att.net [12.122.145.33]
18 108 ms 107 ms 108 ms 12-122-254-14.attens.net [12.122.254.14]
19 108 ms 109 ms 107 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.13
0.0.170]
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
I’m exasperated!
-
-
Inappropriate?Been absolutely AWFUL for 4 days now, game is unplayable. Considering switching my isp.
Tracing route to 206.17.111.128 over a maximum of 30 hops
1 1 ms 5 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 9 ms 9 ms 68.85.131.197
4 10 ms 9 ms 9 ms po-10-ur08.mtprospect.il.chicago.comcast.net [68.87.231.70]
5 13 ms 11 ms 12 ms be-50-ar01.area4.il.chicago.comcast.net [68.87.230.53]
6 15 ms 11 ms 14 ms pos-1-13-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.49]
7 29 ms 13 ms 14 ms pos-0-1-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.38]
8 13 ms 13 ms 11 ms ber1-tengig3-4.chicagoequinix.savvis.net [208.173.180.45]
9 12 ms 23 ms 14 ms ber2-te-1-0-1.chicagoequinix.savvis.net [204.70.194.230]
10 12 ms 14 ms 11 ms savvis-gw.cgcil.ip.att.net [192.205.35.41]
11 44 ms 40 ms 40 ms cr2.cgcil.ip.att.net [12.122.132.138]
12 40 ms 43 ms 41 ms cr1.n54ny.ip.att.net [12.122.1.1]
13 41 ms 40 ms 40 ms cr2.n54ny.ip.att.net [12.122.2.14]
14 41 ms 40 ms 40 ms cr1.cb1ma.ip.att.net [12.122.31.126]
15 38 ms 40 ms 40 ms gar5.cb1ma.ip.att.net [12.122.145.29]
16 42 ms 40 ms 43 ms 12-122-254-14.attens.net [12.122.254.14]
17 41 ms 40 ms 40 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.130.0.170]
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. -
-
Inappropriate?HI. Same problem here. For what we pay Comcast should seek to resolve this issure asap!
----
Q u o t e:
There is sporadic packet loss and some spiking on the images, that combined with the traceroute points to an issue on the route.
Regardless of where the issue starts it would be your ISP that you would need to contact.
If the issue occurs outside of their network they would need to work with their peering partners to investigate the issue. You may need to ask for a tier 2 or 3 technician for assistance with this.
----
I’m upset / frustrated
-
Inappropriate?same problem...
fix please.
washington IL -
Inappropriate?Both Tues & Wed nights (around 6pm Pacific), I DC'd in raid due to high latency, and was replaced by another member of my guild :( Traceroute shows it dropping at ATT. I called Comcast both nights, and the technicians were nice on both calls. The Tues night the tech reset the connection...didn't help. Tonight the tech said he'd escalate the case to the next tier. Hope the problem is fixed before raid again tomorrow night!!! The Blizzard forums are running 32+ pages deep with complaints of this problem occuring with the peering of Comcast, AT&T WorldNet Services, and Savvis.
I've been playing WoW via a Comcast connection for over 2.5 years now, and this is the first time I've had this problem!
Palo Alto, CA
I’m frustrated & furious
-
Inappropriate?Same exact problem as above. This needs to be fixed for the amount of money I pay comcast. I really only use high speed inet for WoW. If this isn't fixed in the next day or so I'm switching providers for both tv and high speed inet.
I’m frustrated/upset
-
Inappropriate?Same here...since sunday night.
Tracing route to 206.17.111.83 over a maximum of 30 hops
1 * * * Request timed out.
2 8 ms 10 ms 9 ms ge-1-1-ur01.hayward.ca.sfba.comcast.net [68.87.196.129]
3 9 ms 8 ms 8 ms te-9-1-ur02.hayward.ca.sfba.comcast.net [68.87.192.86]
4 9 ms 9 ms 9 ms te-0-8-0-1-ar01.oakland.ca.sfba.comcast.net [68.87.192.90]
5 11 ms 11 ms 12 ms pos-0-4-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.90.141]
6 13 ms 13 ms 12 ms pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.181]
7 13 ms 14 ms 14 ms er1-tengig2-4.sanjoseequinix.savvis.net [206.24.222.1]
8 14 ms 14 ms 15 ms pr2-ge-2-0-0.SanJoseEquinix.savvis.net [204.70.200.130]
9 17 ms 16 ms 16 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
10 105 ms 104 ms 103 ms cr1.sffca.ip.att.net [12.122.137.126]
11 102 ms 103 ms 102 ms cr1.cgcil.ip.att.net [12.122.4.122]
12 105 ms 104 ms 105 ms cr2.cgcil.ip.att.net [12.122.2.54]
13 * 108 ms 108 ms cr1.n54ny.ip.att.net [12.122.1.1]
14 104 ms 103 ms 102 ms cr2.n54ny.ip.att.net [12.122.2.14]
15 107 ms * * cr1.cb1ma.ip.att.net [12.122.31.126]
16 104 ms 105 ms 102 ms gar5.cb1ma.ip.att.net [12.122.145.33]
17 * 109 ms 109 ms 12-122-254-14.attens.net [12.122.254.14]
18 104 ms 104 ms 105 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.130.0.170
I’m irate...
-
Inappropriate?Here's my tracert info from Michigan (comcast). The trouble all starts at savvis/att. They seem to be having issues. Hope comcast is on it cause now they get a phone call from me and it is not going to be pretty.
1 <1><1><1 ms 192.168
2 13 ms 7 ms 6 ms 73.116.195.1
3 8 ms 22 ms 37 ms ge-3-2-ur02.brighton.mi.michigan.comcast.net [68
85.235.37]
4 8 ms 10 ms 6 ms te-8-1-ur03.brighton.mi.michigan.comcast.net [68
87.190.58]
5 8 ms 7 ms 7 ms te-9-1-ur02.waterford.mi.michigan.comcast.net [6
.87.190.70]
6 12 ms 10 ms 12 ms te-9-3-ur03.waterford.mi.michigan.comcast.net [6
.87.190.74]
7 8 ms 11 ms 8 ms te-8-1-ur02.springfield.mi.michigan.comcast.net
68.87.190.122]
8 28 ms 15 ms 8 ms te-0-4-0-6-ar01.pontiac.mi.michigan.comcast.net
68.87.190.126]
9 37 ms 28 ms 21 ms pos-2-1-0-0-cr01.chicago.il.ibone.comcast.net [6
.86.90.109]
10 26 ms 22 ms 23 ms 68.86.86.78
11 29 ms 36 ms 31 ms ber1-tengig3-3.chicagoequinix.savvis.net [208.17
.180.41]
12 49 ms 29 ms 31 ms ber2-te-1-0-1.chicagoequinix.savvis.net [204.70.
94.230]
13 24 ms 23 ms 30 ms savvis-gw.cgcil.ip.att.net [192.205.35.41]
14 84 ms 86 ms 96 ms cr1.cgcil.ip.att.net [12.122.133.142]
15 93 ms 87 ms 84 ms cr2.dvmco.ip.att.net [12.122.31.85]
16 84 ms 92 ms 85 ms cr1.slkut.ip.att.net [12.122.30.25]
17 88 ms 90 ms 85 ms cr2.la2ca.ip.att.net [12.122.30.30]
18 85 ms 85 ms 84 ms gar5.la2ca.ip.att.net [12.122.129.25]
19 93 ms 91 ms 86 ms 12.122.255.74
20 86 ms 94 ms 94 ms 12.129.193.242
I’m beyond irate
-
Inappropriate?Same issues. f'ing comcast
-
Inappropriate?Just called comcast, not their problem and Blizzard hasn't opened a trouble ticket with comcast at all on this issue.
I’m frustrated
-
Inappropriate?Yeah, I called ComCast as well...multiple times. I was told since the problem is on the other side of a peer, it's not their issue and to call Savvis or AT&T, neither of whom will speak to me or tell me anything, let alone look at anything, because I'm not a customer of theirs.
I’m venomously angry at this point...
-
Inappropriate?It is a AT&T and Savvis issue not comcast. Savvis and AT&T won't talk to end users, only Bliz can pressure them and I'm tired of the run around. Done.
I’m po'ed
-
Inappropriate?Taken this morning
comcast
chicago, il
area52
Tracing route to 206.16.147.108 over a maximum of 30 hops
1 7 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 18 ms 9 ms 7 ms 68.85.131.193
4 10 ms 9 ms 20 ms be-50-ar01.area4.il.chicago.comcast.net [68.87.2
30.53]
5 19 ms 18 ms 11 ms pos-1-12-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.90.53]
6 19 ms 11 ms 11 ms pos-0-1-0-0-pe01.350ecermak.il.ibone.comcast.net
[68.86.86.38]
7 12 ms 18 ms 15 ms 75.149.228.250
8 16 ms 26 ms 11 ms if-2-0-0-18.core1.CT8-Chicago.as6453.net [66.110
.14.33]
9 10 ms 13 ms 30 ms 192.205.33.165
10 38 ms 37 ms 39 ms cr2.cgcil.ip.att.net [12.122.132.142]
11 45 ms 44 ms 44 ms cr1.n54ny.ip.att.net [12.122.1.1]
12 41 ms 47 ms 44 ms cr2.n54ny.ip.att.net [12.122.2.14]
13 40 ms 37 ms 49 ms cr1.cb1ma.ip.att.net [12.122.31.126]
14 42 ms 41 ms 39 ms gar5.cb1ma.ip.att.net [12.122.145.33]
15 41 ms 43 ms 45 ms 12-122-254-14.attens.net [12.122.254.14]
16 40 ms 40 ms 49 ms 12.130.0.174
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. -
Inappropriate?I am in the Chicago West Suburbs. Same exact issue. Latency extremely high and when a raid boss is engadged, I get diconnected ever 10-15 seconds.
Here is a link to one of the threads in the Warcraft Support forums. Plenty of information there. http://forums.worldofwarcraft.com/thr...
I’m tired of lag and disconnects.
-
Inappropriate?Issues are still persisting.. Howell, Michigan
Savvis has been removed from the routing table and it looks like the last IP addys have changed - I have no idea where those are from. Probably being routed to Asia or something stupid.
Tracing route to us.logon.worldofwarraft.com [220.125.208.228]
over a maximum of 30 hops:
1 2 ms <1><1 ms 192.168.1.1
2 9 ms 7 ms 19 ms 73.116.195.1
3 12 ms 6 ms 8 ms ge-3-2-ur02.brighton.mi.michigan.comcast.net [68
.85.235.37]
4 7 ms 7 ms 8 ms te-8-1-ur03.brighton.mi.michigan.comcast.net [68
.87.190.58]
5 9 ms 7 ms 8 ms te-9-1-ur02.waterford.mi.michigan.comcast.net [6
8.87.190.70]
6 13 ms 18 ms 7 ms te-9-3-ur03.waterford.mi.michigan.comcast.net [6
8.87.190.74]
7 10 ms 8 ms 10 ms te-8-1-ur02.springfield.mi.michigan.comcast.net
[68.87.190.122]
8 14 ms 9 ms 10 ms te-0-4-0-6-ar01.pontiac.mi.michigan.comcast.net
[68.87.190.126]
9 24 ms 21 ms 27 ms pos-2-1-0-0-cr01.chicago.il.ibone.comcast.net [6
8.86.90.109]
10 44 ms 46 ms 53 ms pos-2-15-0-0-cr01.atlanta.ga.ibone.comcast.net [
68.86.85.166]
11 65 ms 64 ms 65 ms pos-1-14-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.153]
12 98 ms 110 ms 104 ms pos-0-13-0-0-cr01.losangeles.ca.ibone.comcast.ne
t [68.86.85.145]
13 103 ms 98 ms 99 ms kornet.la.comcastlink.kornet.net [68.86.88.2]
14 225 ms 215 ms 213 ms 220.73.154.93
15 212 ms 212 ms 213 ms 59.18.63.61
16 222 ms 228 ms 213 ms 59.18.52.13
17 218 ms 214 ms 216 ms 220.73.153.102
18 230 ms 306 ms 336 ms 211.225.217.126
19 * * * Request timed out.
I’m sick and tired
-
Inappropriate?Haha! Here is the response I recently recieved from Blizzard;
"Unfortunately even though our servers are in the AT&T Network, we do not supply your internet connection, and therefore are unable to escalate the issue for you. Also, since you are not a direct customer of AT&T you are unable to speak to them as well. However, since your ISP is a Customer of AT&T and does supply your internet connection, I would recommend contacting your ISP directly and having them escalate the issue for you. Please be sure to show them the tracer route as proof of the connection issue.
If for any reason they say they cannot escalate the issue for you (have heard that a few times), this is not the case, they are fully capable of doing that. Simply ask to have the issue escalated to a higher level representative. "
**********
Here's the buck, please pass along. I have a feeling this is not going to get resolved.
I’m at the end of my rope
-
Inappropriate?Yay 3 days in a row with a good connection. Nothing changed on my side...looks like they resolved whatever was going on
-
Inappropriate?Same here. Not only did they fix the prblem but now
my connection is faster than before. I also followed this advice (check out link below) and reset my modem.
http://shadowweaving.wordpress.com/20...
I’m satisfied
-
Inappropriate?Seems like they did do something to fix things. Comcast customer service reps very polite and knowledgeable. Bliz, not so much.
I’m excited
-
Inappropriate?If you look at a traceroute, they now go through a different provider than Savvis. All has been well from SF since Thursday.
-
Inappropriate?This issue is not resolved for me in Baltimore, Maryland. Still constantly at 250-320ms while playing World of Warcraft.
I’m beyond frustrated after 2 weeks of this.
-
Inappropriate?This was fixed for a few days (traffic was rerouted), but now I am again getting disconnects.
I’m frustrated
-
Inappropriate?Happening to me too in Jacksonville Florida, here are 2 tracerts taken June 3rd.
Tracing route to 206.17.111.6 over a maximum of 30 hops
1 * * * Request timed out.
2 6 ms 7 ms 8 ms te-9-2-sr02.southside.fl.jacksvil.comcast.net [68.86.171.197]
3 7 ms 6 ms 9 ms te-1-1-sr01.southside.fl.jacksvil.comcast.net [68.86.168.245]
4 8 ms 6 ms 7 ms te-7-4-ar01.southsiderdc.fl.jacksvil.comcast.net [68.86.168.113]
5 16 ms 18 ms 14 ms te-0-2-0-5-ar03.pompanobeach.fl.pompano.comcast.net [68.85.229.229]
6 14 ms 14 ms 17 ms pos-0-7-0-0-ar03.northdade.fl.pompano.comcast.net [68.86.164.5]
7 15 ms 18 ms 16 ms pos-0-5-0-0-cr01.miami.fl.ibone.comcast.net [68.86.91.81]
8 31 ms 31 ms 30 ms pos-2-3-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.85.193]
9 51 ms 51 ms 58 ms pos-1-11-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.221]
10 55 ms 53 ms 53 ms a190103.sandpiper.net [206.82.142.5]
11 59 ms 51 ms 56 ms Vlan6.icore1.DTX-Dallas.as6453.net [209.58.47.13]
12 52 ms 52 ms 52 ms 192.205.35.57
13 78 ms 81 ms 79 ms cr2.dlstx.ip.att.net [12.122.138.114]
14 81 ms 82 ms 79 ms cr1.attga.ip.att.net [12.122.28.173]
15 80 ms 78 ms 79 ms cr2.wswdc.ip.att.net [12.122.1.174]
16 80 ms 80 ms 78 ms cr2.n54ny.ip.att.net [12.122.3.37]
17 83 ms 78 ms 78 ms cr1.cb1ma.ip.att.net [12.122.31.126]
18 84 ms 81 ms 78 ms gar5.cb1ma.ip.att.net [12.122.145.33]
19 130 ms 199 ms 206 ms 12-122-254-14.attens.net [12.122.254.14]
20 100 ms 79 ms 78 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.130.0.170]
21 * * * Request timed out.
And another one.
Tracing route to 206.17.111.6 over a maximum of 30 hops
1 <1><1><1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 8 ms 7 ms te-9-2-sr02.southside.fl.jacksvil.comcast.net [68.86.171.197]
4 10 ms 8 ms 9 ms te-7-1-ar01.westside.fl.jacksvil.comcast.net [68.86.168.129]
5 9 ms 10 ms 8 ms te-7-2-ar01.southsiderdc.fl.jacksvil.comcast.net [68.86.168.126]
6 16 ms 18 ms 21 ms te-0-2-0-6-ar03.pompanobeach.fl.pompano.comcast.net [68.86.164.25]
7 20 ms 15 ms 16 ms pos-0-7-0-0-ar03.northdade.fl.pompano.comcast.net [68.86.164.5]
8 17 ms 16 ms 16 ms pos-0-3-0-0-cr01.miami.fl.ibone.comcast.net [68.86.91.221]
9 30 ms 31 ms 30 ms pos-2-3-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.85.193]
10 51 ms 52 ms 52 ms pos-1-12-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.157]
11 52 ms 52 ms 52 ms a190103.sandpiper.net [206.82.142.5]
12 52 ms 54 ms 53 ms Vlan6.icore1.DTX-Dallas.as6453.net [209.58.47.13]
13 51 ms 52 ms 52 ms 192.205.35.57
14 78 ms 79 ms 78 ms cr2.dlstx.ip.att.net [12.122.138.114]
15 78 ms 78 ms 79 ms cr1.attga.ip.att.net [12.122.28.173]
16 78 ms 79 ms 78 ms cr2.wswdc.ip.att.net [12.122.1.174]
17 79 ms 78 ms 83 ms cr2.n54ny.ip.att.net [12.122.3.37]
18 78 ms 78 ms 79 ms cr1.cb1ma.ip.att.net [12.122.31.126]
19 80 ms 78 ms 78 ms gar5.cb1ma.ip.att.net [12.122.145.33]
20 79 ms 79 ms 79 ms 12-122-254-14.attens.net [12.122.254.14]
21 79 ms 78 ms 82 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]
22 * * * Request timed out.
300+ms in game is horrible. -
Inappropriate?Tracing route to uswest.battle.net [63.241.83.107]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.10.1
2 74 ms 74 ms 57 ms 73.107.252.1
3 81 ms 91 ms 68 ms ge-1-1-sr01.losalamos.nm.albuq.comcast.net [68.8
5.224.161]
4 96 ms 125 ms 75 ms pos-3-0-0-sr01.santafe.nm.albuq.comcast.net [68.
86.182.125]
5 303 ms 308 ms 304 ms pos-5-0-0-ar01.albuquerque.nm.albuq.comcast.net
[68.86.182.97]
6 316 ms 327 ms 315 ms te-0-6-0-4-cr01.denverqwest.co.ibone.comcast.net
[68.86.91.25]
7 296 ms 283 ms 301 ms te-0-1-0-1-cr01.santateresa.tx.ibone.comcast.net
[68.86.84.70]
8 285 ms 292 ms 330 ms pos-1-8-0-0-cr01.losangeles.ca.ibone.comcast.net
[68.86.86.13]
9 335 ms 306 ms 297 ms Vlan547.icore2.LAA-LosAngeles.as6453.net [216.6.
12.25]
10 * 320 ms 306 ms Vlan1130.icore1.LAA-LosAngeles.as6453.net [216.6
.12.14]
11 314 ms 311 ms 320 ms 192.205.35.129
12 305 ms 298 ms 324 ms cr2.la2ca.ip.att.net [12.122.129.30]
13 329 ms 326 ms 316 ms gar4.la2ca.ip.att.net [12.122.129.169]
14 351 ms 363 ms 353 ms idf26-gsr12-1-pos-6-0.rwc1.attens.net [12.122.25
5.122]
15 287 ms 283 ms 296 ms mdf2-bi8k-2-eth-1-1.rwc1.attens.net [216.148.209
.18]
16 * * * Request timed out.
17 * * * Request timed out.
etc,etc
Going on 4(?) weeks now.
It starts out fine around 200ms at 6pm, and ends up unplayable by 9pm 600 or higher, constant disconnects, sucks for tanking.
I’m frustrated
-
Inappropriate?I'm having the same issues. I've had 2 techs out to check everything on my end. It all checks out as good.
Is comcast ever going to address this?
Great Lakes, IL -
Inappropriate?Several people in my guild are disconnecting or having horrible lag at identical times about every 20 minutes. Vent or any other web program has been unaffected..just wow. We realized tonight that all the people having the problem have Comcast. Most are from the east coast oddly. I'm in utah but getting the diconnects at the same time as they are.
Also, my latency is regularly at around 280 ms on wow, which is rather high , but it's jumped to 350+ over the past few days this problem has been occurring.
I can also say it happens more frequently during prime hours (evenings).
Sorry, but this is just too coincidental to not be a comcast/wow problem.
Whatever you need to do to fix it, please do so. Another night of trying to raid like this and I'm afraid I'm done with comcast.
I’m grrr
-
Inappropriate?Yes, here we are again. This continues and nobody is taking ownership of the issue - just look at the tech support forums at Bliz. I'm tired of comcast and Bliz at this point. I'm done with both companies. Funny how I can play any other online game and not have any lag issues or disconnection issues. I will be moving away from Bliz and tomorrow morning I'm calling a new cable/satellite tv company.
I’m ticked off beyond belief!
