Traceroute fails at Blizz gateway?

Technical Support
Tracing route to 63.240.104.93 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms
2 34 ms 28 ms 21 ms
3 11 ms 11 ms 11 ms te-2-2-ur01.phoenixville.pa.panjde.comcast.net [68.85.152.61]
4 42 ms 65 ms 11 ms xe-5-1-0-0-ar03.coatesville.pa.panjde.comcast.net [68.86.209.149]
5 12 ms 10 ms 12 ms ae-7-0-ar03.newcastle.de.panjde.comcast.net [69.139.193.209]
6 38 ms 18 ms 19 ms pos-5-13-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.141]
7 14 ms 19 ms 15 ms pos-0-5-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.87.14]
8 18 ms 23 ms 19 ms 192.205.37.41
9 23 ms 23 ms 24 ms cr1.wswdc.ip.att.net [12.122.113.42]
10 40 ms 39 ms 19 ms cr2.phlpa.ip.att.net [12.122.4.53]
11 20 ms 18 ms 35 ms gar1.pitpa.ip.att.net [12.122.107.85]
12 28 ms 26 ms 26 ms 12.122.251.2
13 38 ms 21 ms 18 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 12.129.202.154 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms
2 94 ms 22 ms 22 ms
3 10 ms 8 ms 12 ms te-2-2-ur01.phoenixville.pa.panjde.comcast.net [68.85.152.61]
4 25 ms 13 ms 11 ms xe-5-1-0-0-ar03.coatesville.pa.panjde.comcast.net [68.86.209.149]
5 15 ms 13 ms 11 ms ae-8-0-ar03.newcastle.de.panjde.comcast.net [69.139.193.213]
6 21 ms 14 ms 19 ms pos-5-10-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.92.177]
7 16 ms 33 ms 15 ms pos-0-0-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.26]
8 19 ms 19 ms 51 ms 192.205.37.41
9 85 ms 103 ms 83 ms cr2.wswdc.ip.att.net [12.122.134.186]
10 85 ms 83 ms 87 ms cr1.cgcil.ip.att.net [12.122.18.21]
11 88 ms 82 ms 84 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 84 ms 86 ms 84 ms cr1.slkut.ip.att.net [12.122.30.25]
13 87 ms 86 ms 87 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 165 ms 217 ms 82 ms gar29.la2ca.ip.att.net [12.122.129.241]
15 86 ms 85 ms 86 ms 12.122.251.190
16 84 ms 83 ms 100 ms 206.16.68.46
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.
Hey Slyther,

The timeouts at the end of the trace are normal, as we have set our network to not respond to traces:
Because of the safeguards that protect our Battle.net servers, you may notice later hops in your trace route failing with an error message such as 'Request Timed Out' or 'Destination Net Unreachable'. You may also see inflated latency numbers. You can ignore any error messages you receive after contacting our servers as they do not indicate a problem with your internet connection. To identify our servers, look for the following suffixes: attens.net, att.net, alter.net, telia.net.

I do see one spike in latency on Hop 14 of the last trace. I would a pathping for more detail.

Are you lagging in game?

If you're using a router, I'd bypass that too, just as a test, and connect directly to the modem.
________________________________________________
Monday - Friday, 8 am - 5 pm PST
Pelinti
I start the game at 140 fps and after a few moments it drops to 0-10 fps and I have to alt-f4

This started after patch 1.5

I did bypass the router and I've gone as far as temporarily uninstalling antivirus. I play Diablo 3 with no problems, and every other online game for that matter. Just SC2 is the problem.
Indeed...
Can you post a pathping, Slyther?
________________________________________________
Monday - Friday, 8 am - 5 pm PST
Pelinti
I've also been having a similar problem.

Blizz rep told me to contact my ISP lol. I am doubtful that that would be fruitful.

Tracing route to 12.129.202.154 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 10.0.0.1
3 8 ms 10 ms 9 ms 96.153.68.1
4 9 ms 10 ms 11 ms te-9-3-ur01.boston.ma.boston.comcast.net [68.87.157.53]
5 12 ms 15 ms 11 ms be-60-ar01.needham.ma.boston.comcast.net [68.85.69.49]
6 25 ms 23 ms 23 ms he-2-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.94.201]
7 15 ms 15 ms 16 ms pos-0-0-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.87.122]
8 21 ms 22 ms 20 ms 192.205.37.33
9 107 ms 91 ms 91 ms cr1.n54ny.ip.att.net [12.122.131.86]
10 92 ms 91 ms 94 ms cr2.cgcil.ip.att.net [12.122.1.2]
11 89 ms 91 ms 91 ms cr1.cgcil.ip.att.net [12.122.2.53]
12 91 ms 90 ms 91 ms cr2.dvmco.ip.att.net [12.122.31.85]
13 102 ms 91 ms 91 ms cr1.slkut.ip.att.net [12.122.30.25]
14 92 ms 91 ms 99 ms cr2.la2ca.ip.att.net [12.122.30.30]
15 90 ms 90 ms 181 ms gar29.la2ca.ip.att.net [12.122.129.241]
16 92 ms 90 ms 89 ms 12.122.251.190
17 88 ms 93 ms 98 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.
Pathping:

Tracing route to 12.129.202.154 over a maximum of 30 hops

0 [MyPC]
1 192.168.1.1
2 10.0.0.1
3 96.153.68.1
4 te-9-3-ur01.boston.ma.boston.comcast.net [68.87.157.53]
5 be-60-ar01.needham.ma.boston.comcast.net [68.85.69.49]
6 he-2-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.94.201]
7 pos-0-0-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.87.122]
8 192.205.37.33
9 cr1.n54ny.ip.att.net [12.122.131.86]
10 cr2.cgcil.ip.att.net [12.122.1.2]
11 cr1.cgcil.ip.att.net [12.122.2.53]
12 cr2.dvmco.ip.att.net [12.122.31.85]
13 cr1.slkut.ip.att.net [12.122.30.25]
14 cr2.la2ca.ip.att.net [12.122.30.30]
15 gar29.la2ca.ip.att.net [12.122.129.241]
16 12.122.251.190
17 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
18 * * *
Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Antonio-PC [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% 96.153.68.1
0/ 100 = 0% |
4 9ms 0/ 100 = 0% 0/ 100 = 0% te-9-3-ur01.boston.ma.boston.comcast.net [68.87.157.53]
0/ 100 = 0% |
5 14ms 0/ 100 = 0% 0/ 100 = 0% be-60-ar01.needham.ma.boston.comcast.net [68.85.69.49]
0/ 100 = 0% |
6 22ms 0/ 100 = 0% 0/ 100 = 0% he-2-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.94.201]
0/ 100 = 0% |
7 18ms 0/ 100 = 0% 0/ 100 = 0% pos-0-0-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.87.122]
0/ 100 = 0% |
8 20ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.33
100/ 100 =100% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr1.n54ny.ip.att.net [12.122.131.86]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.1.2]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.2.53]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.190
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]

Trace complete.
Your traces look good, GreenSage. But I do see you're using a router, and I would bypass the router just for now, and connect straight to the modem, and test playing that way, and see if there's a difference in game.
________________________________________________
Monday - Friday, 8 am - 5 pm PST
Pelinti
Are you sure those timeouts are OK?

In any case, I am having connectivity issues in general, but I think it might be better to make a new thread on it so I'm going to do that. :)

Join the Conversation

Return to Forum