For the past 3 weeks I have been having very annoying issues with intermittent packet loss and an even more annoying issue trying to get comcast to fix it. I live in central NJ, and have had 5 conversations with comcast VIA online chat and 2 phone conversations, all resulting in frustration and 0 progress towards a fix.
I have replaced every cable in the network from the PC to the main jack into the house, and had no better results. The first analyst I talked to just refreshed my connection 5 times until he got a good health report and assured me everything was fixed even after I reminded him it was an intermittent issue, happening a few times over a few minutes. (I play an Online game so this proves to render gamely impossible.)
The second analyst have me flip flop my coax cable around, and did more refreshing. This rep also assured me the problem was fixed.
The third analyst informed me my modem was out of date and that was the issue, replace it and, you guessed it, assured me it would remedy the problem. I got a brand new modem, installed it, had comcast activate it (which was an endeavor in itself), same problem.
Fourth analyst just shoved me off saying there was maintenance in the area and it would be complete the following morning at 8am. I have no way of knowing if this was true but either way it did not fix my issue.
Called the first time and the rep was all over the place and obviously had no idea what the internet was let alone how to fix it.
Fifth analyst had no idea what I was talking about when I mentioned packet loss, which was no surprise seeing as hed ended every statement or instruction he made with a question mark, and wrote in broken English. (annoying) So he said a tech would be calling the house in the next 24-72 hours....After I informed him I have a job and cannot be around for 72 hours...yada yada yada, I left the chat.
Last interaction was a phone call that was going in the same direction as the last and at this point I couldn't take anymore without getting irate so I asked to speak to a tech but instead obtained a home visit appointment, which I think is a step forward. Or so I thought, until browsing these forums and coming to realize that after 4 tech visits most people with this issue have yet to get a fix.
So my root question is, has anyone figured out what a common cause for intermittent packet loss with comcast is, or something I should ask the tech to check?
Ping results (Only did 30 so as not to make this any longer, I usually do 250 and return an average of 233):
PING 130.102.2.15 (130.102.2.15): 56 data bytes
64 bytes from 130.102.2.15: icmp_seq=0 ttl=40 time=835.267 ms
64 bytes from 130.102.2.15: icmp_seq=1 ttl=40 time=652.669 ms
64 bytes from 130.102.2.15: icmp_seq=2 ttl=40 time=267.460 ms
64 bytes from 130.102.2.15: icmp_seq=3 ttl=40 time=268.436 ms
64 bytes from 130.102.2.15: icmp_seq=4 ttl=40 time=251.385 ms
64 bytes from 130.102.2.15: icmp_seq=5 ttl=40 time=542.092 ms
64 bytes from 130.102.2.15: icmp_seq=6 ttl=40 time=360.327 ms
64 bytes from 130.102.2.15: icmp_seq=7 ttl=40 time=468.078 ms
64 bytes from 130.102.2.15: icmp_seq=8 ttl=40 time=250.860 ms
64 bytes from 130.102.2.15: icmp_seq=9 ttl=40 time=268.044 ms
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
64 bytes from 130.102.2.15: icmp_seq=15 ttl=40 time=8010.678 ms
64 bytes from 130.102.2.15: icmp_seq=17 ttl=40 time=6009.095 ms
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
64 bytes from 130.102.2.15: icmp_seq=19 ttl=40 time=9262.822 ms
64 bytes from 130.102.2.15: icmp_seq=23 ttl=40 time=5259.553 ms
64 bytes from 130.102.2.15: icmp_seq=24 ttl=40 time=4258.559 ms
64 bytes from 130.102.2.15: icmp_seq=25 ttl=40 time=3258.004 ms
64 bytes from 130.102.2.15: icmp_seq=26 ttl=40 time=2257.733 ms
64 bytes from 130.102.2.15: icmp_seq=28 ttl=40 time=256.097 ms
64 bytes from 130.102.2.15: icmp_seq=21 ttl=40 time=7262.197 ms
64 bytes from 130.102.2.15: icmp_seq=27 ttl=40 time=1257.029 ms
64 bytes from 130.102.2.15: icmp_seq=29 ttl=40 time=278.491 ms
--- 130.102.2.15 ping statistics ---
30 packets transmitted, 21 packets received, 30.0% packet loss
round-trip min/avg/max/stddev = 250.860/2454.042/9262.822/2908.872 ms