Visitor

 • 

1 Message

Thursday, November 13th, 2025 10:56 PM

Is Comcast aware of the horrible packet loss in the Denver/Littleton, CO Area?

<html><head><title>WinMTR Statistics</title></head><body bgcolor="white">
<center><h2>WinMTR statistics</h2></center>
<p align="center"> <table border="1" align="center">
<tr><td>Host</td> <td>%</td> <td>Sent</td> <td>Recv</td> <td>Best</td> <td>Avrg</td> <td>Wrst</td> <td>Last</td></tr>
<tr><td>192.168.1.1</td> <td>   0</td> <td>  51</td> <td>  51</td> <td>   0</td> <td>   0</td> <td>   3</td> <td>   0</td></tr>
<tr><td>cm-1-acr04.littleton.co.denver.comcast.net</td> <td>   0</td> <td>  51</td> <td>  51</td> <td>   8</td> <td>  19</td> <td>  38</td> <td>  12</td></tr>
<tr><td>po-254-1222-rur202.littleton.co.denver.comcast.net</td> <td>   0</td> <td>  51</td> <td>  51</td> <td>   8</td> <td>  19</td> <td>  40</td> <td>  10</td></tr>
<tr><td>po-2-rur201.littleton.co.denver.comcast.net</td> <td>   0</td> <td>  51</td> <td>  51</td> <td>   7</td> <td>  19</td> <td>  40</td> <td>  12</td></tr>
<tr><td>po-200-xar01.littleton.co.denver.comcast.net</td> <td>   0</td> <td>  51</td> <td>  51</td> <td>   8</td> <td>  19</td> <td>  39</td> <td>  12</td></tr>
<tr><td>be-304-arsc1.denver.co.denver.comcast.net</td> <td>   0</td> <td>  51</td> <td>  51</td> <td>   8</td> <td>  20</td> <td>  41</td> <td>  12</td></tr>
<tr><td>be-36021-cs02.1601milehigh.co.ibone.comcast.net</td> <td>  60</td> <td>  15</td> <td>   6</td> <td>   0</td> <td>  25</td> <td>  40</td> <td>  11</td></tr>
<tr><td>be-2411-pe11.champa.co.ibone.comcast.net</td> <td>   0</td> <td>  51</td> <td>  51</td> <td>   9</td> <td>  21</td> <td>  37</td> <td>  11</td></tr>
<tr><td>No response from host</td> <td> 100</td> <td>  11</td> <td>   0</td> <td>   0</td> <td>   0</td> <td>   0</td> <td>   0</td></tr>
<tr><td>17.0.78.64</td> <td>   0</td> <td>  51</td> <td>  51</td> <td>  10</td> <td>  21</td> <td>  45</td> <td>  11</td></tr>
<tr><td>usden5-vip-bx-003.aaplimg.com</td> <td>   0</td> <td>  51</td> <td>  51</td> <td>   9</td> <td>  21</td> <td>  37</td> <td>  13</td></tr>
</table></body></html>

Oldest First
Selected Oldest First

Gold Problem Solver

 • 

26.9K Messages

4 days ago

[... horrible packet loss ...]

Host % Sent Recv Best Avrg Wrst Last
192.168.1.1 0 51 51 0 0 3 0
cm-1-acr04.littleton.co.denver.comcast.net 0 51 51 8 19 38 12
po-254-1222-rur202.littleton.co.denver.comcast.net 0 51 51 8 19 40 10
po-2-rur201.littleton.co.denver.comcast.net 0 51 51 7 19 40 12
po-200-xar01.littleton.co.denver.comcast.net 0 51 51 8 19 39 12
be-304-arsc1.denver.co.denver.comcast.net 0 51 51 8 20 41 12
be-36021-cs02.1601milehigh.co.ibone.comcast.net 60 15 6 0 25 40 11
be-2411-pe11.champa.co.ibone.comcast.net 0 51 51 9 21 37 11
No response from host 100 11 0 0 0 0 0
17.0.78.64 0 51 51 10 21 45 11
usden5-vip-bx-003.aaplimg.com 0 51 51 9 21 37 13

51 packets were sent and 51 received, meaning the "loss" is more apparent than real. Your trace shows no packet loss at the destination. The apparent loss at hops along the way are probably not significant.  

Please see https://web.archive.org/web/20230802010554/https://www.dslreports.com/faq/14068:

Why am I seeing so much packet loss in my provider's network?

If you are also seeing packet loss from these points all the way to the final hop of your test, that points to a problem on the device first showing packet loss or on the inbound connection to that device. However, if you are not seeing packet loss all the way to the final hop, this apparent packet loss may not be an issue.
Some providers are rate-limiting how often they respond with the TTL-exceeded ICMP packets used by traceroute and similar tools like the Packet Loss Test. This is done to prevent attacks against these routers, since responding to these packets requires much more CPU time than simply forwarding the packet does. If the router is set up to rate-limit, it will respond to a certain number of traceroute packets per second, and once that many have been received, it will stop responding to them for that second -- which will appear as packet loss. You are not losing any "real" traffic, assuming the final hop of your traceroute isn't showing any loss.

The fact that hops after the "loss" hops are receiving packets indicates that the routers are doing their job: forwarding data packets. The 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 the following hops, and we don't. You may indeed have a communication problem, but the traces do not show that.

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.

Official Employee

 • 

637 Messages

2 days ago

Hey there user_u5mgh3, and thanks for making us aware of the issues you're noticing with the internet service! I know how crucial it is to have my internet at peak performance at all times, so if that hasn't been the case for you, then we'll definitely do what we can to help 👍

How are things in the home performing for you since creating your post? Are you still noticing packet loss?

forum icon

New to the Community?

Start Here