It worked fine in the past, and continues to have intermittent issues. I am also pursuing my internet provider connection though the tech that came out says the signal is good. I have cleared the cookies and memory in the TV, and I am not sure, other than the normal reboot (soft and hard) procedures for the Hopper 3, what other steps to take. The problem with this kind of issue is having it happen when a tech is monitoring. Intermittent issues are the worst! That's why I asked the original question to see if others were seeing the same type of problem.
It would help if we knew the following, who your internet provider is and what exact speed product are you using? Also, what make/model equipment is involved is there between where the internet providers connection and the Hopper 3 + Hopper Plus? As for the tech, they are measuring the signal which only will show the signal quality between your connection and their network. What you do not know is the routing or networks it is using to reach the destination that is streaming the data to you as the issue might not even be with your Internet Service Provider but the actual path it takes for the packets going between you and the destination (DISH) and it is both directions as your equipment will always send back a ACKnowledgement packet to the destination that it has received the packet.
There is no single fixed IP address on the remote end, because a DISH Hopper 3 connects to a distributed mix of DISH-owned infrastructure and third-party cloud/CDN servers depending on what it is doing.
Remote IP Ranges by Traffic Type
• DISH Core Infrastructure & Relay Servers. DISH Network Corporation operates under AS13996, which owns roughly 3,328 IPv4 addresses. Control traffic, authorization, guide data, and Dish Anywhere relay handshakes commonly route through DISH's primary 66.170.240.0/20 block (such as 66.170.240.x through 66.170.252.x) and 67.214.63.x.
• On Demand (IPVOD) & Signal-Loss Streaming. Actual video streams for DISH On Demand and internet fallback do not come from a single static IP. Instead, they are delivered dynamically via major Content Delivery Networks (CDNs) like Akamai, Amazon CloudFront/AWS, and Fastly, meaning the destination IPs rotate frequently based on your geographic location and ISP routing.
• Built-in Third-Party Apps. If you are streaming through apps on the Hopper 3 or Hopper Plus (such as Netflix, YouTube, or Prime Video), the receiver connects directly to those respective providers' CDN edge servers.
As for what else you can try, what hard procedure are you speaking of? If it's hitting the reset button, that does not turn off the power to the circuits so there will still be some in the NVRAM. What you need to do is hold down the "power" button on the Hopper 3 itself for 20-30 seconds, this is the same thing as pulling the power cord and plugging it back in but without needing to do it as it Forces a Complete Memory Flush, Holding the physical power button down continuously for 20 to 30 seconds acts as a hard system interrupt. It completely discharges the residual voltage from the internal capacitors and forces the motherboard to drop all temporary system states and cached background logs before the software can write a persistent safety checkpoint. When you hit reset or do the menu reboot, it instructs the Linux operating system to save its active state to the NVRAM so it can resume whatever it was doing upon startup. Try that to see if it makes a difference but if you already did the power cord pull, then it shouldn't.