If you're having trouble connecting to GitHub, you can troubleshoot your connection, then use the GitHub Debug tool to diagnose problems.

Most often, connection problems occur because a firewall, proxy server, corporate network, or other network is configured in a way that blocks GitHub.

Whitelisting GitHub's IP addresses

Make sure your network is configured to whitelist GitHub's IP addresses. For more information, see "About GitHub's IP addresses."

Using a company or organization's network

If you're having connectivity problems on your company or organization's network, check with your network administrator to find out if the network has rules in place to block certain traffic. If there are rules in place, ask your network administrator to whitelist traffic to GitHub.

Switching cloning methods

Switching from cloning via SSH to cloning via HTTPS, or vice versa may improve connectivity. For more information, see "Cloning a repository from GitHub."

If you're encountering timeouts with SSH, see "Error: Bad file number."

Troubleshooting slow downloads and intermittent slow connections

GitHub does not throttle bandwidth per user.

If you're experiencing slow connections at certain times of day but not others, the slow speeds are most likely due to network congestion. Because GitHub cannot resolve network congestion, you should escalate the problem to your internet service provider.

Troubleshooting with GitHub Debug

If you've followed all of the troubleshooting suggestions above and are still having connection problems, you can follow the instructions on the GitHub Debug site to run tests and send a report to GitHub Support. For more information, see GitHub Debug.