This appears to be an issue between global crossing and Comcast in the
Los Angeles area. Filtering comcast routes from our gblx transit
ports and resolved the issue now routing via level3.
On Jul 17, 2008, at 5:49 PM, Logan Rawlins wrote:
I have various customers complaining of comcast issues and from
traces i've seen so far it looks to be isolated to comcast or their
handoff to someone. Anyone else having these issues and can a
comcast network engineer please contact me off list if possible
thanks.
Tracing route to [64.38.193.22]
over a maximum of 30 hops:
1 15 ms 18 ms 17 ms 192.168.1.1
2 * * * Request timed out.
3 17 ms 9 ms 27 ms ge-1-7-
ur01.seattle.wa.seattle.comcast.net [68.8
6.99.65]
4 11 ms 11 ms 23 ms te-8-4-
ar01.burien.wa.seattle.comcast.net [68.86
.96.189]
5 17 ms 15 ms 21 ms 68.86.90.222
6 14 ms 31 ms 17 ms 68.86.90.221
7 28 ms 27 ms 46 ms pos-0-6-0-0-
cr01.sacramento.ca.ibone.comcast.net
[68.86.85.197]
8 32 ms 47 ms 42 ms pos-0-7-0-0-
cr01.sacramento.ca.ibone.comcast.net
[68.86.85.181]
9 40 ms * 48 ms te-1-1-
pr01.11greatoaks.ca.ibone.comcast.net [68
.86.84.126]
10 109 ms 54 ms 154 ms 68.86.88.250
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
-Logan
