Visitor

 • 

1 Message

Wednesday, May 20th, 2026 3:26 PM

Out-of-spec downstream power + documented 48hr degradation — requesting line technician

Good catch — let me give you the full version with everything Winter has gathered. This is the stronger post.

Category: Your Home Network Topic/sub-category: Internet (or "Connection Issues" if available)


Subject: Out-of-spec downstream power + documented 48hr degradation — requesting line technician

Body:

Service plan: Gigabit Extra (~941/43 Mbps) Modem: Arris Surfboard S33v2 (DOCSIS 3.1), firmware TB01.03.001.11 Location: Mount Laurel, NJ

I have 48 hours of continuous documented evidence showing intermittent service degradation with root cause on the plant side. Summary below; full diagnostic logs available via DM.

Modem signal readings (current):

  • Downstream Signal Power: -11 dBmV (DOCSIS spec: -7 to +7 dBmV — out of spec by 4 dB)
  • Downstream Signal SNR: 35 dB (minimum for QAM256: 36 dB — below spec)
  • Downstream Frequency: 567 MHz

Throughput delivery (48hr continuous speedtest sampling, wired host):

  • Measured: 512–704 Mbps down, 32–38 Mbps up
  • Delivered: 54–75% of provisioned plan
  • Consistent under-delivery across all sampling windows, not transient

Latency analysis (continuous ping monitoring, 5-second interval to 1.1.1.1 and 8.8.8.8):

  • Idle baseline: 16–21ms
  • Spikes to 244ms under load
  • 9 of 10 recent 5-minute windows flagged with elevated latency (20–46ms average)

Traceroute analysis (every 2 hours):

  • Hop 2 (Comcast CMTS): 14–29ms latency variance — modem-to-node segment
  • Hop 9 (Newark peering): occasional packet loss
  • Latency variance originates at Hop 2 = plant-side, not in-home

Bufferbloat testing (Waveform.com, wired):

  • Current grade: A under controlled conditions (SQM on home router)
  • Peak loaded latency observed: 244ms during degradation events
  • Pattern: ~80% of time within spec, ~20% degraded — consistent with intermittent plant issue

In-home equipment ruled out:

  • All tests run from wired host behind professional-grade gateway (Ubiquiti UDM Pro)
  • Smart Queue Management (CAKE) enabled on WAN with confirmed correct algorithm
  • DNS, switching, and WiFi all verified clean
  • Throughput and latency degradation occur regardless of in-home load

Diagnosis: Downstream power 4 dB below DOCSIS spec, combined with SNR below QAM256 minimum, is consistent with attenuation on the drop or tap side. The intermittent nature of latency spikes and throughput drops, combined with Hop 2 variance, indicates plant-side instability — likely corroded F-connector, damaged drop, water-damaged tap port, or attenuation from upstream amplifier.

Request:

Please dispatch a line technician for plant-side signal investigation at the tap and amplifier serving my address.

I am specifically not requesting:

  • A modem swap (modem is reporting accurately and functioning correctly given signal received)
  • An in-home technician visit (issue is documented upstream of demarc)
  • A modem reboot (already verified; signal levels persist)

Happy to provide full diagnostic logs (PDF report with continuous ping data, MTR traces, speedtest history, and bufferbloat measurements) via DM upon request.

Oldest First
Selected Oldest First

Official Employee

 • 

2.8K Messages

5 hours ago

 

user_cvxm8s This is an incredibly thorough breakdown, and honestly it is awesome to see how tools like AI can help pull together such detailed analysis and point toward a likely root cause. You’ve clearly put a lot of effort into isolating variables and narrowing this down.

That said, while your findings do suggest a potential issue outside the home, we do still need to follow the standard troubleshooting path step by step. Even when things appear to point upstream, our process requires starting with the basics and working forward so we can properly document everything and ensure nothing is missed along the way.

Because of that, we aren’t able to directly request a line technician right away. The next step would be to go through the standard troubleshooting flow, which typically begins with verifying signal levels, connections, and account diagnostics on our side. Once those steps are completed and documented, we can absolutely look at escalating this further, including getting the right type of technician involved if the issue continues to point to the network or plant.


I definitely understand the goal here and appreciate how much detail you’ve provided. If you’re open to it, we can start with that initial process together and work toward getting this escalated appropriately.

 

forum icon

New to the Community?

Start Here