Recent activity
Subscribe to this feed
Wayne replied on July 25, 2009 06:12 to the problem "warcraft latency Issue returns for May 2k9" in Comcast:
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.
Wayne replied on May 31, 2009 12:47 to the problem "warcraft latency Issue returns for May 2k9" in Comcast:
Wayne replied on May 28, 2009 23:18 to the problem "warcraft latency Issue returns for May 2k9" in Comcast:
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.
Wayne replied on May 28, 2009 20:21 to the problem "warcraft latency Issue returns for May 2k9" in Comcast:
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.
Wayne replied on May 28, 2009 16:35 to the problem "warcraft latency Issue returns for May 2k9" in Comcast:
Wayne replied on May 28, 2009 15:01 to the problem "warcraft latency Issue returns for May 2k9" in Comcast:
Wayne replied on May 28, 2009 12:51 to the problem "warcraft latency Issue returns for May 2k9" in Comcast:
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
Wayne replied on May 28, 2009 12:28 to the problem "warcraft latency Issue returns for May 2k9" in Comcast:
-
Wayne started following the problem "warcraft latency Issue returns for May 2k9" in Comcast.
Loading Profile...
