Of course, I have to deal with crappy connectivity at times.
by any chance you are using Reliance broadnet wireline? ....if yes, then i think i have solution to your problem. I use to face the same issue till few months back. One day i sat with my wireshark and figured out the problem is not the physical connectivity. it is due to:-
1. length of the cable from Fiber box till my house. :- For this you cannot do much, just make sure if you have any extra wire hanging around, then just cut short. Basically the fiber to ethernet switch they are using is not providing enough power to keep packets alive when resistance increases. (generally on sunny days when temperature is more than 35.) (also if you are under 100 mtr, then should not affect you)
2. Incorrect MTU.:- Hit and try, start with 1492 and keep checking the stability.
3. Wrong
DNS pulled up in configuration. :- Make sure you use reliance dns as the primary DNS and you can use secondary as
google or any of your choice. The issue is captive portal implementation from reliance side.
4. Also, if you are terminating ethernet on your
routers WAN port, make sure you router is not overloaded with number of devices. See in my case, I have around 73 different devices, like bunch of
laptops, mobiles
tablets and atleast 50+
raspberry pi device connected. I initially connected multiple SOHO routers together and formed a network. it was creating confusion with NAT. So i simplified then it started overloading the end router. Later i switched to distributed network using
Cisco 2700, now things are sorted. It might not be this bad in your case, but if you have more than 15 devices all landing on a home grade router, then it starts to overload the NAT.
Also, as a best practice, have your router rebooted atleast once in a day. You can use a script to do so if needed.