Skip to main content
Solved

SB8200 Slow Intermittent Connection on Astound Broadband


Forum|alt.badge.img

Similar to other posts, I am experiencing very slow (less than 1Mbps) on a 1GB service through Astound Broadband over last several weeks.  Trying to figure out if it is the ISP, the modem or my wifi.  Not sure how to diagnose modem and hoping someone knows how to decipher this.

 

Best answer by plemans

You have a ton of errors in your line and your logs indicate the same. 

Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.

If these don’t help, the ISP needs to check the line. 

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

6 replies

LoveMyLab
Guardians of the Gateways
Forum|alt.badge.img+19
  • Guardians of the Gateways
  • 210 replies
  • October 17, 2023

Your signal levels are fine. The Signal to Noise is within spec, but at the lower end of the desired range. The question is, why are the uncorrected errors so high? I’d reboot and see what the uncorrected errors are at the end of an hour and report back. Also, what are you seeing in the Event Log? Any T3/T4 Timeouts? Any CMTS warnings? Don’t post any internal MAC information if you post a screen shot.

 

Additionally, to get a good speed check, connect your PC directly to the SB8200 using ethernet. Reboot the SB8200, and run the Ookla Speedtest locally, not in a Chrome or Edge browser window. Let us know what kind of speed results you get that way.


Forum|alt.badge.img
  • Author
  • The Many
  • 2 replies
  • October 17, 2023

Thanks for your assistance on this.  Ran two speed tests, one direct from modem to computer and another using the ISP’s speed test via browser.  Ookla showed 40 Mbps down, 4.87 up.  ISP showed 34 down, 1 Mbps up.  My service should be 1100 Mbps down and 11 Mbps up.  Yesterday, the event log showed no events, but today, after modem reboot, there are many.  See screenshots.  ISP is scheduled to come out tomorrow.  Really would like to resolve this.

 


LoveMyLab
Guardians of the Gateways
Forum|alt.badge.img+19
  • Guardians of the Gateways
  • 210 replies
  • October 18, 2023

The T3 timeouts show there is a definite communication error between your modem and the Cable Modem Termination System (CMTS). You have other errors occuring as well that indicate connection stability issues. Once your ISP addresses the connection, I’d do a hard reset of the unit (with cable disconnected) and then connect and test again.


plemans
Juggernaut
Forum|alt.badge.img+41
  • Juggernaut
  • 2275 replies
  • Answer
  • October 20, 2023

You have a ton of errors in your line and your logs indicate the same. 

Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.

If these don’t help, the ISP needs to check the line. 


Forum|alt.badge.img
  • Author
  • The Many
  • 2 replies
  • October 27, 2023

ISP had equipment in our neighborhood that was bad. Once replaced speeds are back to normal. 


LoveMyLab
Guardians of the Gateways
Forum|alt.badge.img+19
  • Guardians of the Gateways
  • 210 replies
  • October 27, 2023

Thanks for the update! Thought that might be the case.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings