Github is currently working for me via Hughesnet.
I tried the github-debug dot com diagnostics again, and these two errors still occurred, so I guess they are irrelevant.
Two errors that stood out to me were:
- The ssh git clone test also said "The authenticity of host '[github dot com]' (140...4) can't be established."
- A ping test from some github host to my ip address said "Destination Net Unreachable". [this was the 184.xx.xx.xx public ipv4 address which as MarkJFine pointed out, might not work from behind a NAT (network address translation) router, either hughesnet's or github's.]
I believe I've solved the issue.
Like the other posters here, I haven't been able to load pages from Github in my web browser or to use git over HTTPS for some time now. However, I noticed that I can ping Github without any issues (so DNS is resolving correctly and there is a valid network path from my machine to github.com). I also noticed that using git over SSH works perfectly well.
So...it looks like I'm just seeing HTTPS traffic to Github throttled to the point of being unusable most of the time (with some occasional reprieves as mentioned by other posters).
To fix this, I simply created a SOCKS5 proxy to a remote computer (not on HughesNet's network) that I have SSH access to and then configured my web browser to send all web traffic through this proxy. And...voila! Github loads right away. That's all it takes to solve the issue until HughesNet gets their act together and fixes it for the rest of us.
Here are the steps I used:
Step 1: Open an SSH tunnel (on localhost port 1080) to a remote server to use as an HTTP(S) proxy
$ ssh -f -N -D 1080 firstname.lastname@example.org
Step 2: Launch your browser with the proxy enabled (I'm using chromium here)
$ chromium --proxy-server=socks5://localhost:1080
And that's all there is to it.
If you don't have SSH access to a remote server, just look for an HTTP(S) proxy server that you can use. It's all the same in the end. The end goal is to have your browser route all outgoing traffic (over the HughesNet network) to the proxy server and then (over the not-HughesNet network) to your end destination (such as github.com). This allows you to totally dodge the HughesNet-Github bottleneck.
Have fun and happy hacking!
Using open proxies that you've arbitrarily chosen off the internet is a really really bad idea.