I have been experiencing packet loss for about a week now and have been looking at the traceroute results. Im not familiar with how to diagnose the issue here, but it always times out on hop 9.
1 2 ms 2 ms 1 ms Docsis-Gateway.hsd1.pa.comcast.net [10.0.0.1]
2 12 ms 10 ms 11 ms 126.96.36.199
3 8 ms 8 ms 8 ms 188.8.131.52
4 17 ms 19 ms 16 ms be-35-ar01.mckeesport.pa.pitt.comcast.net [184.108.40.206]
5 22 ms 22 ms 23 ms be-7016-cr02.ashburn.va.ibone.comcast.net [220.127.116.11]
6 22 ms 25 ms 23 ms be-1302-cs03.ashburn.va.ibone.comcast.net [18.104.22.168]
7 21 ms 27 ms 21 ms be-2307-pe07.ashburn.va.ibone.comcast.net [22.214.171.124]
8 21 ms 21 ms 20 ms as15169-4-c.ashburn.va.ibone.comcast.net [126.96.36.199]
9 * * * Request timed out.
10 23 ms 25 ms 19 ms google-public-dns-a.google.com [188.8.131.52]
That particular trace is fine. The timeout that you see at hop #9 is not a problem. It is just a router that is deliberately configured to not respond to ICMP packet based ping requests. The trace has completed to its destination.
You should ping and trace to the servers that you are seeing a problem with.
Try performing extended pings to hop number one (your gateway device), and hop number 2 (the Comcast WAN default gateway) / CMTS to help narrow things down.
Is this with a WiFi connection ? If so, for a test, does a computer hardwired directly to the router / gateway device with an ethernet cable have the same problem ?
Do them when the problem is occurring.
Try this command ping -n 100 IP address to ping goes here