O

Thursday, September 19th, 2024 2:06 AM

Ping spikes and Packet Loss

I am having issues with our home network. There is consistent packet loss and ping spikes on this hop: be-309-arsc1.area4.il.chicago.comcast.net [162.151.45.109]

Here are the tracert commands I ran:

C:\Users\richa>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

  1     5 ms     2 ms     1 ms  10.0.0.1
  2    11 ms    11 ms     9 ms  96.120.25.177
  3    12 ms     9 ms    10 ms  po-309-1209-rur301.wchicago.il.chicago.comcast.net [68.87.208.189]
  4    10 ms     9 ms     8 ms  po-2-rur302.wchicago.il.chicago.comcast.net [96.216.150.150]
  5     9 ms     8 ms     8 ms  po-300-xar02.wchicago.il.chicago.comcast.net [96.216.150.41]
  6     *        *        *     Request timed out.
  7    14 ms    19 ms    13 ms  be-502-ar01.area4.il.chicago.comcast.net [96.216.150.118]
  8    20 ms    13 ms    13 ms  c-50-171-101-230.unallocated.comcastbusiness.net [50.171.101.230]
  9    19 ms    13 ms    14 ms  142.250.209.145
 10    14 ms    14 ms    15 ms  142.251.60.17
 11    30 ms    14 ms    13 ms  dns.google [8.8.8.8]

Trace complete.

C:\Users\richa>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

  1     5 ms     1 ms     1 ms  10.0.0.1
  2    51 ms    10 ms    13 ms  96.120.25.177
  3    10 ms     8 ms    10 ms  po-309-1209-rur301.wchicago.il.chicago.comcast.net [68.87.208.189]
  4    15 ms    10 ms     9 ms  po-2-rur302.wchicago.il.chicago.comcast.net [96.216.150.150]
  5     9 ms     9 ms    14 ms  po-300-xar02.wchicago.il.chicago.comcast.net [96.216.150.41]
  6     *        *       39 ms  be-309-arsc1.area4.il.chicago.comcast.net [162.151.45.109]
  7    11 ms    13 ms    13 ms  be-502-ar01.area4.il.chicago.comcast.net [96.216.150.118]
  8    15 ms    14 ms    14 ms  c-50-171-101-230.unallocated.comcastbusiness.net [50.171.101.230]
  9    16 ms    13 ms    13 ms  142.250.209.145
 10    16 ms    20 ms    13 ms  142.251.60.17
 11    18 ms    15 ms    19 ms  dns.google [8.8.8.8]

Trace complete.

C:\Users\richa>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

  1     4 ms     2 ms    <1 ms  10.0.0.1
  2    11 ms     9 ms    11 ms  96.120.25.177
  3    18 ms    15 ms     9 ms  po-309-1209-rur301.wchicago.il.chicago.comcast.net [68.87.208.189]
  4    12 ms     8 ms     8 ms  po-2-rur302.wchicago.il.chicago.comcast.net [96.216.150.150]
  5    15 ms     8 ms     8 ms  po-300-xar02.wchicago.il.chicago.comcast.net [96.216.150.41]
  6     *        *        *     Request timed out.
  7    14 ms    12 ms    12 ms  be-502-ar01.area4.il.chicago.comcast.net [96.216.150.118]
  8    17 ms    17 ms    14 ms  c-50-171-101-230.unallocated.comcastbusiness.net [50.171.101.230]
  9    24 ms    16 ms    13 ms  142.250.209.145
 10    13 ms    13 ms    13 ms  142.251.60.17
 11    14 ms    13 ms    20 ms  dns.google [8.8.8.8]

Trace complete.

Gold Problem Solver

 • 

26K Messages

2 months ago

Trace packets are reaching the target, so the "loss" at hop 6 is likely more apparent than real, and probably not significant. Please see https://www.dslreports.com/faq/14068. The fact that hops beyond than ones you are concerned received the trace packets indicates that the router at that address is doing its job: forwarding data packets. The hop 6 router's occasional delay in or failure to respond to trace packets, while annoying, is most likely not actually slowing down data transfer. If it was we'd see high RTT values and/or packet loss in all subsequent hops.

Interpreting trace results is tricky. What appears to be "late" or is reported as "lost" could mean 1) the packet did not reach or was delayed in reaching that hop, or 2) the router at that hop didn't reply or was slow to reply, or 3) the reply from that hop didn't make it back or was delayed in making it back to the trace program.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

10 Messages

I've seen you reply this comment to multiple people with the same issue as me and I think it's reductive. 

There is consistent packet loss and no matter how many times the home equipment is replaced, nothing changes. It is an issue on Xfinity's end and it should be fixed. There are numerous other threads where people are having issues in the Chicagoland area. 

Gold Problem Solver

 • 

26K Messages

2 months ago

... I think it's reductive ...

Not really. I'm not Comcast and have no way of knowing how that router is programed or of running diagnostics on it. All I have to work with is the trace information posted, and, as explained previously, it is not consistent with what we'd expect to see if the router was causing packet loss and ping spikes. It's possible that the router is misbehaving, but if it is the traces don't show that.

The most we can say is that trace packets sent to that router are not resulting in the response packets we'd expect to see. Why, we can only guess, and my best guess is that the router is programmed to give low priority to trace packets. Comcast could determine what's happening here, but that would cost them a few pennies, so it would surprise me if they bothered to check. Regrettably, in 17 years of reading these forums, I've never seen them respond to the many, many similar complaints.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

Official Employee

 • 

1K Messages

2 months ago

@Odyssey34 Is this happening when you're doing a specific task (like working, streaming, gaming etc)?

10 Messages

It is happening during all of the above. It is consistent throughout the entire day. There are few complete drops in connection/service, but it makes it especially difficult to work from home.

We have replaced the router within the last three months and the issue was mitigated but not solved. It has since increased in severity. When the ping/packet loss spikes voice calls cut out for a moment, games freeze, websites stop loading, etc. 

(edited)

Official Employee

 • 

1.4K Messages

Hello @Odyssey34, thank you for taking the time to reach out on social media. 

 I rely on my internet daily and can appreciate you wanting it to work consistently. I'd be happy to run some troubleshooting for you today. Troubleshooting can also be done through the My Account App or online at https://www.xfinity.com/support/internet#troubleshooting.

 

 

To access your account, will you please send us a direct message with your full name and complete service address.

To do so, click on the chat icon located at the top right of this forums page.

Here's the detailed steps to direct message us:

  • Click "Sign In" if necessary
  • Click the "Direct Message” icon (upper right corner of this page)
  • Click the "New message" (pencil and paper) icon
  • Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list
  • Type your message in the text area near the bottom of the window
  • Press Enter to send your message
I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

10 Messages

@XfinityKrista​ I have reached out through the direct message system.

10 Messages

1 month ago

I took a trip to the store and replaced the router. The issue is still there. 

Official Employee

 • 

1.4K Messages

Hello @Odyssey34, thank you for taking the time to reach out on social media.  I understand your concern with the connection, and I'd like the opportunity to check into that for you.

To access your account, will you please send us a direct message with your full name and complete service address.

To do so, click on the chat icon located at the top right of this forums page.

Here's the detailed steps to direct message us:

  • Click "Sign In" if necessary
  • Click the "Direct Message” icon (upper right corner of this page)
  • Click the "New message" (pencil and paper) icon
  • Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list
  • Type your message in the text area near the bottom of the window
  • Press Enter to send your message
I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

10 Messages

@XfinityKrista​ I have already done this. 

10 Messages

22 days ago

The issue went away for about a week and it has now returned. 

10 Messages

22 days ago

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  10.0.0.1
  2    11 ms     9 ms     8 ms  96.120.25.177
  3    13 ms     8 ms    12 ms  po-309-1210-rur302.wchicago.il.chicago.comcast.net [69.139.184.29]
  4    11 ms     9 ms     9 ms  po-300-xar02.wchicago.il.chicago.comcast.net [96.216.150.41]
  5     *        *        *     Request timed out.
  6    16 ms    22 ms    14 ms  be-501-ar01.area4.il.chicago.comcast.net [96.216.150.114]
  7    34 ms    27 ms    18 ms  c-50-171-101-226.unallocated.comcastbusiness.net [50.171.101.226]
  8    17 ms    12 ms    12 ms  142.250.209.27
  9    14 ms    15 ms    15 ms  142.251.60.201
 10    17 ms    12 ms    12 ms  dns.google [8.8.8.8]

Trace complete.

C:\Users\richa>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  10.0.0.1
  2    18 ms     8 ms    17 ms  96.120.25.177
  3    12 ms     8 ms    10 ms  po-309-1210-rur302.wchicago.il.chicago.comcast.net [69.139.184.29]
  4    14 ms    10 ms     9 ms  po-300-xar02.wchicago.il.chicago.comcast.net [96.216.150.41]
  5     *        *       77 ms  be-309-arsc1.area4.il.chicago.comcast.net [162.151.45.109]
  6    13 ms    13 ms    12 ms  be-501-ar01.area4.il.chicago.comcast.net [96.216.150.114]
  7    18 ms    13 ms    17 ms  c-50-171-101-226.unallocated.comcastbusiness.net [50.171.101.226]
  8    13 ms    11 ms    12 ms  142.250.209.27
  9    15 ms    14 ms    14 ms  142.251.60.201
 10    16 ms    16 ms    17 ms  dns.google [8.8.8.8]

10 Messages

22 days ago

This same node is continually causing issues. 

be-309-arsc1.area4.il.chicago.comcast.net [162.151.45.109]

Official Employee

 • 

999 Messages

@Odyssey34 Welcome back. As others have mentioned, this doesn't signify an issue with that part of the network. You will see that type of behavior on our network all over the country. Those hops deal with an incredible amount of traffic. They sometimes have to prioritize which packets receive a response and which are just routed to the next hop. As long as your end destination doesn't show packet loss, you are good to go in that regard. We use some really cool technology to make sure those main hops stay up and efficient.

Since you are having real world problems with your internet, we definitely want to keep troubleshooting it. I received your DM and will be responding there shortly.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick
forum icon

New to the Community?

Start Here