Severe intermittent packet loss and routing delays traced to Miami backbone node (be-33841-cs24.nota.fl.ibone.comcast.net)

Hello,

For months I have been experiencing ongoing connection reliability issues, including intermittent packet loss, dropped connections, and severe ping spikes.

To isolate the issue, I bypassed all Wi-Fi variables and hardwired my PC directly via Ethernet to my routing setup. Local network communication is completely flawless, but continuous tracing exposes a severe breakdown deep inside the Comcast infrastructure.

Here are the diagnostic details:

Local Loop Health: Hop 1 shows 0% packet loss and a 0ms average response time across hundreds of samples, ruling out my local router, cables, and PC.
The Root Issue: Severe 75% packet loss consistently begins at the regional Comcast backbone node: be-33841-cs24.nota.fl.ibone.comcast.net.
Latency Spikes: Severe latency degradation (up to 120ms+) introduces right before hitting this backbone switch.

Below is the exact WinMTR log showing the infrastructural failure in the Pompano/North Dade, FL routing path:

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| [Local Deco Router] - 0 | 241 | 241 | 0 | 0 | 3 | 0 |

| [Comcast Internal Node 1] - 0 | 241 | 241 | 4 | 11 | 24 | 10 |

|po-111-rur501.northdade.fl.pompano.comcast.net - 0 | 241 | 241 | 5 | 12 | 23 | 13 |

|po-2-rur502.northdade.fl.pompano.comcast.net - 0 | 241 | 241 | 4 | 11 | 23 | 10 |

|po-500-xar02.northdade.fl.pompano.comcast.net - 0 | 241 | 241 | 4 | 12 | 29 | 7 |

|be-302-arsc1.northdade.fl.pompano.comcast.net - 0 | 241 | 241 | 5 | 13 | 120 | 12 |

| be-33841-cs24.nota.fl.ibone.comcast.net - 75 | 62 | 16 | 0 | 15 | 21 | 13 |

| be-2411-pe11.nota.fl.ibone.comcast.net - 1 | 237 | 236 | 4 | 12 | 33 | 13 |

| No response from host - 100 | 50 | 0 | 0 | 0 | 0 | 0 |

| [Google Gateway 1] - 0 | 241 | 241 | 6 | 14 | 97 | 13 |

| [Google Gateway 2] - 0 | 241 | 241 | 7 | 14 | 37 | 14 |

| dns.google - 0 | 241 | 241 | 5 | 12 | 28 | 12 |

|________________________________________________|______|______|______|______|______|______|

Responses

Oldest First

Selected Oldest First

U

user_MM10

Visitor

•

3 Messages

2 days ago

Additionally, when it rains, the reliability of the internet connection gets even worse.

0

U

user_MM10

Visitor

•

3 Messages

1 day ago

Test from today on Wi-Fi: 46% packet loss @ be-33841-cs24.nota.fl.ibone.comcast.net

I have yet another technician appointment set for Saturday AM but they will not be able to fix it. I need this escalated to the right team, please!

The same technician has asked twice for bucket truck support to check the lines, but not a single bucket truck has come to check the nodes or distribution amplifier that is in front of my house.

Thank you!

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.XX.X - 0 | 377 | 377 | 6 | 31 | 216 | 22 |
| 10.146.XXX.XXX - 0 | 377 | 377 | 11 | 44 | 233 | 40 |
|po-111-rur501.northdade.fl.pompano.comcast.net - 0 | 377 | 377 | 11 | 42 | 200 | 29 |
|po-2-rur502.northdade.fl.pompano.comcast.net - 0 | 378 | 378 | 11 | 40 | 188 | 17 |
|po-500-xar02.northdade.fl.pompano.comcast.net - 0 | 377 | 377 | 12 | 42 | 194 | 28 |
|be-302-arsc1.northdade.fl.pompano.comcast.net - 0 | 377 | 377 | 17 | 53 | 326 | 29 |
| be-33841-cs24.nota.fl.ibone.comcast.net - 46 | 134 | 73 | 18 | 45 | 219 | 31 |
| be-2411-pe11.nota.fl.ibone.comcast.net - 0 | 378 | 378 | 15 | 52 | 312 | 22 |
| No response from host - 100 | 76 | 0 | 0 | 0 | 0 | 0 |
| 142.251.77.73 - 0 | 377 | 377 | 16 | 55 | 316 | 59 |
| 216.239.51.215 - 0 | 377 | 377 | 12 | 52 | 320 | 59 |
| dns.google - 0 | 377 | 377 | 14 | 52 | 320 | 59 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

1

0

BruceW

Gold Problem Solver

•

27.5K Messages

12 hours ago

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 the final hop received all 377 trace 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 through all of the following hops, and we don't. You may indeed have a communication problem, but the trace does 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.

Note that the first hop at 192.168.XX.X, with and average RTT of 31 ms and a max of 216 ms (!!) suggests a problem within your home. The RTTs to your home device should be no more than a few ms.

(edited)

0

Your Home Network

user_MM10

Severe intermittent packet loss and routing delays traced to Miami backbone node (be-33841-cs24.nota.fl.ibone.comcast.net)

user_MM10

user_MM10

BruceW

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

New to the Community?