Recurring Connectivity Issues in MS

We have a Comcast Business Class account in Ridgeland, Mississippi 39157 that was set up about 2 months ago.

We have been experiencing constant connectivity issues with the service, so we set up a monitoring solution to graph the connection's latency and loss.

This is a graph of the connection over the last two days, as seen from a monitoring server in Fremont, CA:

Really poor, right?! You can see connectivity losses regularly.

A traceroute from our site in Fremont, CA looks like this:

traceroute 74.93.135.217
traceroute to 74.93.135.217 (74.93.135.217), 30 hops max, 40 byte packets
 1  10.1.1.1 (10.1.1.1)  0.227 ms  0.185 ms  0.177 ms
 2  184.105.233.129 (184.105.233.129)  7.191 ms  8.854 ms  9.012 ms
 3  v913.core2.fmt2.he.net (64.62.145.97)  14.123 ms  14.091 ms  14.215 ms
 4  10gigabitethernet8-4.core1.fmt2.he.net (184.105.213.189)  8.015 ms  8.108 ms  17.426 ms
 5  10gigabitethernet1-1.core1.sjc2.he.net (72.52.92.74)  10.203 ms  10.172 ms  13.765 ms
 6  Port-channel100.ar3.SJC2.gblx.net (64.214.174.245)  9.082 ms  9.064 ms  8.313 ms
 7  te8-2-10G.ar4.SJC2.gblx.net (67.16.141.70)  8.993 ms  3.014 ms  3.096 ms
 8  e9-3-20G.ar5.SJC2.gblx.net (67.16.142.210)  4.374 ms  4.430 ms  3.654 ms
 9  208.178.58.10 (208.178.58.10)  6.367 ms 208.178.58.6 (208.178.58.6)  5.763 ms 208.178.58.14 (208.178.58.14)  6.445 ms
10  pos-2-5-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.87.17)  9.028 ms  9.381 ms  8.638 ms
11  pos-2-10-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.87.190)  18.861 ms  18.210 ms  17.455 ms
12  he-0-9-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.87.254)  57.717 ms  56.199 ms  55.506 ms
13  pos-0-13-0-0-ar02.dannythomas.tn.malt.comcast.net (68.86.93.98)  62.958 ms  62.928 ms  62.915 ms
14  te-7-1-ur03.jacksonnorth.ms.malt.comcast.net (68.86.241.178)  66.023 ms  65.889 ms  65.181 ms
15  te-3-0-0-ten01.jacksonnorth.ms.malt.comcast.net (68.85.54.78)  64.954 ms  68.774 ms  70.075 ms
16  c-174-50-12-11.hsd1.ms.comcast.net (174.50.12.11)  79.703 ms  73.831 ms  72.710 ms
17  * * *

Given this traceroute, I've configured the monitoring server to also watch each router/hop along the way. Here's a graph of the hop right before our modem connection (174.50.12.11):

And the router before that (68.85.54.78):

This shows that there is a problem after router 68.85.54.78. It may be a poor connection between it and 174.50.12.11, or 174.50.12.11 might be the faulty link.

Regardless, I've written Comcast about this, and called in, and didn't get anywhere. The front-line techs don't understand any of this (understandably), and unfortunately I haven't been able to get past them.

I'd love to hear from a Comcast tech who can look into this. If we can't get it resolved we'll be forced to move to another service, which isn't something we want to do. And this issue is likely affecting many other customers in the area.

Thanks in advance for any support you can provide!

Brett