Comcast XFINITY → [Connectivity] Packet Loss and High Latency

So, I am going well past 2 weeks of nowhere with Comcast Tech people, so here goes:
Recently, as far back as 2 weeks ago and some change, I have been getting DC'd from my online gaming, and my connection speed has drastically dropped. I did my own trouble shooting and this is what I came up with (as Comcast always just resets Modem, and never calls back).
Reinstalled Windows 7, all service packs, all new drivers, etc., got a brand spanking new Modem from Comcast. All 100% fine.
Ran a 'tracert' and 'pathping' to server I always connect to (found problems) and, 2nd and 3rd hop 'always' lose up to 100% sent/recieved packets. (included)
I notified Comcast, they scheduled tech to come out to house. tech checked Modem, connections, wiring, plate, etc. Other than NOT being grounded, gave me a 100% a-ok from house to pole.
However, he said that my 'upstream @ the tap is 48.75, which is, obviously, 'extremely high'. He said he couldn't do anything for me at this point, as maintenance had to come out and check tap(s) and/or line(s) from pole to pole. The problem is NOT on my end, it is 'definitely' on their end.
Now, I have to wait yet 'another' week for them to come out and 'check' (not fix). In the meantime, I attend college full-time, and 'need' my Internet. I keep getting DC'd and/or very very slow connections. Customer service for Comcast gets an "F" from me, as all the phone people wanted to do is 'reset' the Modem and that's it. Last girl I spoke with told me the weather messes up the connection at times, and I made 'sure' she knew how rediculous she sounded. She also actually told me she will NOT put a supervisor on the phone for me either. Hence this forum.
BTW: since I got the 'new' modem, phone techs have reset it at the 'minimum' 12 times in last 6 days. (yes, I keep calling for help)
It's evident that phone support does NOT listen to customers, and just go through the motions implemented by their guidebooks on hand.
So, "where do I go from here"? Verizon said they would come out right away and give me a dedicated line. I won't get the speeds I get from Comcast, but I will stay connected.
Talk to me Comcast. What ya gonna do??? been a Comcast customer/supporter for over 11 years. I don't wanna jump ship, but your leaving me no options here.

I have the same problems as in Frederick MD. I'm on a business so the supports and techs are little more sincere but they have also given me the same answer. Its not on my end they say and they can't do anything about my upstream either.

The pingpath and traceroute you submitted does not point to a problem on Comcast's network. It points to a problem between hops 13 and 14 on the traceroute. After attens.net, which is AT&T.

Can you show another pingpath or traceroute or winmtr results that show packet loss originating on Comcast's network?

How are your tests to other hosts other than 199.107.6.172?

BTW, that appears to be a Battle.net NYC datacenter. Perhaps it is currently of the affected Sandy datacenters, as I can also not get to that IP.

Summary: The results you submitted don't appear to be a problem on the Comcast network.

I have no clue about what protocol is being served on that IP address, so I can't attempt to connect; but a tracert from San José, California, starting from a different network, dies at a neighboring router:

Tracing route to 199.107.6.172 over a maximum of 30 hops
 
  1     1 ms    <1 ms     1 ms  homeportal [192.168.42.1]
  2    25 ms    25 ms    25 ms  173-228-7-1.dsl.static.sonic.net [173.228.7.1]
  3    25 ms    24 ms    24 ms  gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
  4    25 ms    24 ms    24 ms  0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
  5    25 ms    25 ms    25 ms  0.xe-6-1-0.gw2.200p-sf.sonic.net [64.142.0.109]
  6    26 ms    26 ms    25 ms  as0.gw.200p-sf.sonic.net [208.106.96.249]
  7    26 ms    26 ms    26 ms  xe-10-1-0.bar2.SanFrancisco1.Level3.net [4.53.134.9]
  8    26 ms    25 ms    26 ms  ae-6-6.ebr2.SanJose1.Level3.net [4.69.140.154]
  9    29 ms    25 ms    27 ms  ae-92-92.csw4.SanJose1.Level3.net [4.69.153.30]
 10    26 ms    37 ms    25 ms  ae-4-90.edge2.SanJose1.Level3.net [4.69.152.207]
 11    28 ms    28 ms    27 ms  192.205.32.209
 12   102 ms   101 ms   102 ms  cr1.sffca.ip.att.net [12.122.114.6]
 13   104 ms   103 ms   103 ms  cr1.cgcil.ip.att.net [12.122.4.122]
 14   103 ms   101 ms   103 ms  cr1.cl2oh.ip.att.net [12.122.2.206]
 15   103 ms   102 ms   102 ms  cr2.cl2oh.ip.att.net [12.122.2.126]
 16   103 ms   102 ms   102 ms  cr2.phlpa.ip.att.net [12.122.2.210]
 17    99 ms    99 ms    99 ms  gar1.pitpa.ip.att.net [12.122.107.85]
 18   103 ms   103 ms   103 ms  12.122.251.2
 19   101 ms   102 ms   102 ms  mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
 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.
 

This may be caused by trouble at the remote server, or may not. For example, I can pull a page at www.msn.com, but I can't trace it:

Tracing route to us.co1.cb3.glbdns.microsoft.com [131.253.13.140]
over a maximum of 30 hops:
 
  1     1 ms    <1 ms    <1 ms  homeportal [192.168.42.1]
  2    24 ms    26 ms    23 ms  173-228-7-1.dsl.static.sonic.net [173.228.7.1]
  3    24 ms    25 ms    24 ms  gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
  4    24 ms    25 ms    26 ms  0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
  5    24 ms    25 ms    25 ms  0.xe-6-0-0.gw3.equinix-sj.sonic.net [64.142.0.185]
  6    26 ms    50 ms    26 ms  8075.microsoft.com [206.223.116.17]
  7    26 ms    26 ms    26 ms  ge-0-1-0-0.sjc-64cb-1b.ntwk.msn.net [207.46.40.221]
  8    48 ms    31 ms    26 ms  xe-7-2-1-0.by2-96c-1a.ntwk.msn.net [207.46.40.138]
  9    48 ms    48 ms    47 ms  ge-5-2-0-0.co2-64c-1a.ntwk.msn.net [207.46.40.84]
 10    48 ms    47 ms    47 ms  xe-0-0-0-0.co2-96c-2a.ntwk.msn.net [207.46.43.67]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 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.
 

Your tracert to that server may be normal for that server.