Forum Discussion
Echostar 24 implementation - beam #68 overloaded
How long will it take to implement Echostar 24 after it is launched? the launch date is 7/23/23. How long will it take to transfer Hughesnet users to this new beam(s)? I am currently on beam...
KEJ wrote:Hughesnet engineering stated that my slow speed is caused by overloaded beam #68 and there will be no relief until Echostar 24 is operational.
I hope that the person who told you this is mistaken and it's instead a problem that can be remedied, for both yours and maratsade's sakes and everyone else that's on beam 68.
Though I can't say for sure, it seems to me like the problems with this beam came on suddenly, not gradually. With a beam becoming overloaded, as in to the point that it causes more than a typical prime time slowdown, you'd normally see it happen over time, as more subscribers are added. The speed issues with beam 68 seems like they happened literally overnight.
"I hope that the person who told you this is mistaken and it's instead a problem that can be remedied, for both yours and maratsade's sakes and everyone else that's on beam 68."
I hope so too. Fingers crossed!
I am also on 68. Had been out of town while this was being discussed, but am back now.
I did notice some degradation before I left where it seemed as if I was in constant FAP, even though there was plenty of data left and the cycle had just restarted a couple of days before. We're talking all times of day, including Bonus time. Best I can tell, that has since been cleared up, because Bonus time is giving me in excess of 30Mbps on all Linux and macOS updates.
However, there are times where it almost seems as if a bunch of people got new video doorbells, left them running in HD, and they were constantly running. The congestion, particularly in the evenings, is less than optimal. It's manifested itself in terms of lag time, not really speed (e.g. some initial buffering on Amazon Prime or the occasional missed connection due to a timeout) but nothing that's consistently clamped my system to below 1kbps.If it's much worse than what I'm seeing, I suspect there may be something else afoot here, since we're all on the same beam.
Maybe it is maintenance that involves swapping out IPGW servers or turbo buffers and the IPGWs available are reduced.
Could there be some maintenance or upgrades happening at SDO? What about the other beams that share this gateway, like 64 and 66? If folks on beams 64 and 66 also see something like this maybe this is the result of some maintenance at the gateway?
