Skip to main content
user_MM10
1st Topic
1st Reply

Visitor

 • 

8 Messages

Wednesday, July 15th, 2026 2:28 AM

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 |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

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

| [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 |

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

Question

 • 

Updated 

3 days ago

 • Edited

63

3

0

Oldest First
Selected Oldest First
user_MM10

Visitor

 • 

8 Messages

14 days ago

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

0

0

user_MM10

Visitor

 • 

8 Messages

13 days 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

12

0

XfinityVianney

Official Employee

 • 

2.8K Messages

 

user_MM10, Thank you for reaching out and creating a new post. Have you had a chance to reivew @BruceW's input? From our end, have you had any visits in the past year or any tickets opened? Any updates or changes since you made this post?

 

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 as Best Answer.tick

Like

Reply

12 days ago

0

user_MM10

Visitor

 • 

8 Messages

Thanks for the response, @BruceW 

Respectfully, it is definitely not an issue with my home network setup. You might be looking at my earlier Wi-Fi trace. As you can see in my hardwired WinMTR test, my average local latency is 0ms and my maximum spike is only 3ms.

Furthermore, while I understand that backbone routers rate-limit ICMP/TTL traffic (explaining the 75% superficial loss), it does not explain why my maximum latency sharply degrades to 120ms immediately before hitting that switch, nor does it explain the severe real-world drops I am facing.

I've had multiple physical technician visits. They have explicitly confirmed an intermittent issue on the Comcast street line and requested bucket truck/maintenance support, but no one has ever shown up (verified via security cameras).

@XfinityVianney The issue has not been resolved, and I have yet another technician appointment tomorrow AM. I know the local tech can only do so much, but they need to update the maintenance ticket to inspect the physical amplifier outside my house.
This has been going on for months. The symptoms (which get significantly worse whenever it rains) are:
  • Constant dropped packets and severe latency delays while online gaming.
  • Severe pixelation, quality drops, and buffering during streaming and critical work Zoom/MS Teams calls.
  • Frequent dropouts during Wi-Fi calling.

Since a Comcast field technician has already diagnosed a physical line issue, I would deeply appreciate it if an official agent could bypass the basic loops and escalate this directly to the regional maintenance team/NOC.

Thank you.

(edited)

Like

Reply

12 days ago

0

XfinityJamesC

Official Employee

 • 

3K Messages

Thank you for providing this additional insight, @user_MM10. I'm happy to hear the technicians have been submitting requests to have our maintenance team look into this for you. Those types of requests can only be submitted by an onsite technician, so even if they don't find any issues within your house or network, their presence is still absolutely critical to ensure this gets the proper attention. You mentioned having multiple visits about this. Have you had three or more visits in the last 30 days, by any chance?

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 as Best Answer.tick

Like

Reply

12 days ago

0

user_MM10

Visitor

 • 

8 Messages

This might be #3 if not mistaken. What happens after 3 or more?

Like

Reply

11 days ago

0

XfinityKassie

Official Employee

 • 

2.6K Messages

 

user_MM10 Great question! That many appointments in a short period of time is a concern. Over a longer period of time, that can be different issues that arise. Not to say that can't happen within a 30 day window, but we like to keep close tabs on trying to avoid a service issue expanding over several months if possible. I'll check back in later today to see how your appointment went. In the meantime, if anything else comes up on your end, please feel free to let us know. 

 

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 as Best Answer.tick

Like

Reply

11 days ago

0

BruceW

Gold Problem Solver

 • 

27.6K Messages

13 days 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

forum icon

New to the Community?

Start Here