Xfinity plant
Community Forum
Xfinity globe

High Ping/Traceroute

New Poster

High Ping/Traceroute

During some investigation into high ping, it appears that comcast in is routing in a...less than optimal way. When a tracert is run, it's going from AL, to FL, to TX, to CA, and then back to IL. This issue also appears to be resolved when running the test on a network using AT&T so the issue is somewhere within the way comcast is routing everything.

Comcast - Central Trace

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Linksys [192.168.1.1] 
2 8 ms 7 ms 14 ms 96.120.58.xxx 
3 8 ms 8 ms 8 ms po42-rur02.hillcrestprk.al.mobile.comcast.net [68.87.161.253] 
4 9 ms 9 ms 9 ms 162.151.221.166 
5 8 ms 10 ms 8 ms 162.151.221.181 
6 14 ms 12 ms 12 ms ae-32-ar01.mckeithen.fl.tallah.comcast.net [68.85.236.9] 
7 32 ms 33 ms 32 ms be-33666-cr02.dallas.tx.ibone.comcast.net [68.86.90.221] 
8 65 ms 63 ms 63 ms be-11524-cr02.losangeles.ca.ibone.comcast.net [68.86.87.173] 
9 64 ms 62 ms 62 ms be-11587-pe02.600wseventh.ca.ibone.comcast.net [68.86.83.18] 
10 63 ms 62 ms 63 ms 173.167.56.218 
11 63 ms 63 ms 63 ms ae1-br01-eqla1.blizzardonline.net [137.221.68.33] 
12 * * * Request timed out.
13 96 ms 91 ms 91 ms be1-pe01-eqch2.blizzardonline.net [137.221.69.67] 
14 92 ms 91 ms 92 ms 24.105.62.129 

Trace complete.


Comcast - West Coast Trace

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Linksys [192.168.1.1] 
2 8 ms 9 ms 7 ms 96.120.58.xxx 
3 7 ms 8 ms 8 ms po42-rur02.hillcrestprk.al.mobile.comcast.net [68.87.161.253] 
4 8 ms 9 ms 9 ms 162.151.221.166 
5 9 ms 8 ms 8 ms 96.108.32.69 
6 13 ms 22 ms 13 ms ae-32-ar01.mckeithen.fl.tallah.comcast.net [68.85.236.9] 
7 32 ms 34 ms 32 ms be-33666-cr02.dallas.tx.ibone.comcast.net [68.86.90.221] 
8 63 ms 63 ms 63 ms be-11524-cr02.losangeles.ca.ibone.comcast.net [68.86.87.173] 
9 63 ms 64 ms 62 ms be-11587-pe02.600wseventh.ca.ibone.comcast.net [68.86.83.18] 
10 62 ms 71 ms 62 ms 173.167.56.218 
11 65 ms 64 ms 62 ms ae1-br02-eqla1.blizzardonline.net [137.221.68.35] 
12 63 ms 64 ms 62 ms be2-pe01-eqla1.blizzardonline.net [137.221.68.71] 
13 65 ms 64 ms 63 ms 24.105.30.129 

Trace complete.


AT&T - Central Trace

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.2.1] 
2 <1 ms <1 ms <1 ms 192.168.1.254 
3 6 ms 1 ms 1 ms 23-118-32-1.lightspeed.moblal.sbcglobal.net [23.118.32.1] 
4 1 ms 3 ms 1 ms 99.176.76.158 
5 9 ms 7 ms 4 ms 99.15.141.50 
6 2 ms 1 ms 1 ms 99.15.141.79 
7 1 ms 1 ms 1 ms 12.83.106.9 
8 14 ms 14 ms 15 ms 12.122.29.186 
9 15 ms 15 ms 15 ms gar24.attga.ip.att.net [12.122.141.181] 
10 13 ms 12 ms 13 ms 192.205.33.42 
11 9 ms 9 ms 8 ms blizzard-ic-322965-atl-b22.c.telia.net [213.248.78.161] 
12 14 ms 9 ms 9 ms ae1-br01-eqat2.blizzardonline.net [137.221.75.33] 
13 * * * Request timed out.
14 35 ms 34 ms 34 ms be2-pe02-eqch2.blizzardonline.net [137.221.69.73] 
15 31 ms 30 ms 30 ms 24.105.62.129 

Trace complete.
Frequent Visitor

Re: High Ping/Traceroute

I'm having the exact same issue in Panama City, FL. I came to the same conclusion that you did when testing with tracert and pingplotter. Regardless of the game/service, all traffic is routed either halfway or all the way across the us before coming back around to the correct server locations.