Latency spikes

Hi Michael,

I'm having the same problem with my connection (I'm in Mountain View, CA):

Tracert to google.comPing to google.com directly from the modemPing to google.comPing to google.com after modem restart

Hello GFR,

Would you please send me a private message with more details around your service issues, including i you have noted any times of day that the issues occur.

Thank You.

Was a resolution found to your issues?  I am having the same issues after a router swap.  

Are there any real solutions on this site? I keep reading all these issues with connectivity and latency issues but not one solution or real answer. 

Is comcast just legitimately screwing us all over? I cannot get solid connections from my business connection and I pay more than consumer connection prices....

Hello bane_of_my_existence,

Would you please send a private message with your account information so we can trouble shoot further. Thank you.

Hello GAMAS,

Would you please send a private message with your account information so we can trouble shoot further?

I am also having these very same issues.  I recently had incoming broadband calls (VoIP service) shutting down streaming, Internet, and other services.  I ran their diagnostic tools and here is their reply:

Thank you for sending us these results.

We have analyzed them and your connection with our server is showing high latency spikes. Latency refers to the time it takes your network to receive our data. For optimum call quality, you want your
ping speeds to be consistently below 100ms. Here is an example from your test with high latency:

Reply from 50.97.129.83: bytes=32 time=440ms TTL=54
Reply from 50.97.129.83: bytes=32 time=465ms TTL=54
Reply from 50.97.129.83: bytes=32 time=437ms TTL=54
Reply from 50.97.129.83: bytes=32 time=492ms TTL=54
Reply from 50.97.129.83: bytes=32 time=679ms TTL=54
Reply from 50.97.129.83: bytes=32 time=736ms TTL=54
Reply from 50.97.129.83: bytes=32 time=786ms TTL=54
Reply from 50.97.129.83: bytes=32 time=925ms TTL=54
Reply from 50.97.129.83: bytes=32 time=937ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1253ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1127ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1197ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1149ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1150ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1232ms TTL=54
Reply from 50.97.129.83: bytes=32 time=875ms TTL=54
Reply from 50.97.129.83: bytes=32 time=516ms TTL=54
Reply from 50.97.129.83: bytes=32 time=495ms TTL=54
Reply from 50.97.129.83: bytes=32 time=442ms TTL=54
Reply from 50.97.129.83: bytes=32 time=322ms TTL=54
Reply from 50.97.129.83: bytes=32 time=181ms TTL=54
Reply from 50.97.129.83: bytes=32 time=50ms TTL=54
Reply from 50.97.129.83: bytes=32 time=102ms TTL=54
Reply from 50.97.129.83: bytes=32 time=281ms TTL=54
Reply from 50.97.129.83: bytes=32 time=397ms TTL=54
Reply from 50.97.129.83: bytes=32 time=195ms TTL=54
Reply from 50.97.129.83: bytes=32 time=335ms TTL=54
Reply from 50.97.129.83: bytes=32 time=394ms TTL=54
Reply from 50.97.129.83: bytes=32 time=257ms TTL=54
Reply from 50.97.129.83: bytes=32 time=277ms TTL=54
Reply from 50.97.129.83: bytes=32 time=117ms TTL=54
Reply from 50.97.129.83: bytes=32 time=929ms TTL=54
Reply from 50.97.129.83: bytes=32 time=692ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1198ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1301ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1516ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1452ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1504ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1429ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1099ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1340ms TTL=54
Reply from 50.97.129.83: bytes=32 time=1259ms TTL=54

Ping speeds in excess of 100ms can cause interruptions in the call because the data sent is not being received in a timely manner causing delays and choppiness. In addition to latency, there were also packet loss in
your results. Anytime a packet is lost it means the data sent was not received. This causes delays in voice and dropped calls. Below is an example from your test:

Reply from 50.97.129.83: bytes=32 time=159ms TTL=54
Request timed out.
Reply from 50.97.129.83: bytes=32 time=392ms TTL=54
Reply from 50.97.129.83: bytes=32 time=339ms TTL=54
Request timed out.
Reply from 50.97.129.83: bytes=32 time=335ms TTL=54
Reply from 50.97.129.83: bytes=32 time=51ms TTL=54
Request timed out.
Reply from 50.97.129.83: bytes=32 time=279ms TTL=54
Reply from 50.97.129.83: bytes=32 time=53ms TTL=54
General failure.
Reply from 50.97.129.83: bytes=32 time=48ms TTL=54
Reply from 50.97.129.83: bytes=32 time=49ms TTL=54
Request timed out.
Request timed out.
Request timed out.
General failure.
General failure.
General failure.
Reply from 50.97.129.83: bytes=32 time=57ms TTL=54
To rectify this you will need to contact your internet provider and have them diagnose your connection. Let them know you're experiencing high latency and packet loss which is affecting your Voip service and they can troubleshoot with you.

---

@Comcast_Michael wrote:

Hello sferguson,

 

Sorry for the delayed response. Are you still needing assistance with your service? If so please send a private message with more details.

---

Micheal - please check my thread and my reply to this one below.  I still haven't heard anything.

STILL NO CONTACT FROM ANYONE REGARDING THIS LATENCY ISSUE.