Forum Discussion

KEJ's avatar
KEJ
Freshman
2 years ago

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 #68 and my internet is very slow.  A download speed between .17 - 1.31.  Tech services tested the speed and the download speed was 0!!!!!

 

Hughesnet engineering stated that my slow speed is caused by overloaded beam #68 and there will be no relief until Echostar 24 is operational.  When do you expect that to be?

 

thank you.

  • KEJ,

     

    Thank you for reaching out! We would recommend keeping an eye on our social media platforms and website in regards to announcements on our next generation of HughesNet! As the engineering team stated, although we are working to find a solution for beam 68, a complete fix is not expected until the satellite is up and running. In regards to beams 64 and 66, I was unable to find any information regarding ongoing issues with these specific beams. We will continue to keep you updated on new information when we receive it! We appreciate your continued patience, and the updates regarding speed tests and troubleshooting for documentation!

     

    Thanks,

    Remy

  • GabeU's avatar
    GabeU
    Distinguished Professor IV

    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.

    • maratsade's avatar
      maratsade
      Distinguished Professor IV

      "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!

      • MarkJFine's avatar
        MarkJFine
        Professor

        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.

  • maratsade's avatar
    maratsade
    Distinguished Professor IV

    "there will be no relief until Echostar 24 is operational."

     

    I'm on Beam 68 too. That's very bad news, and I'm also curious about when the new satellite will be operational.