As we continue to expand the infrastructure that powers GitHub, we want to make everyone aware of some
changes to the IP addresses that we use. Most customers won’t have to do anything as a result of these
We mentioned these new addresses
back in April and updated the
Meta API to reflect them. Some GitHub services have
have already been migrated to the new addresses, including:
Our next step is to begin using these IP addresses for the main GitHub site, so we’re reminding everyone
about this change. There are a few gotchas that might affect some people:
- If you have explicit firewall rules in place that allow access to GitHub from your network, you’ll want to make sure that all of the IP ranges listed in this article are included.
- If you have an entry in your
/etc/hosts file that points github.com at a specific IP address, you should remove it and instead rely on DNS to give you the most accurate set of addresses.
- If you are accessing your repositories over the SSH protocol, you will receive a warning message each time your client connects to a new IP address for github.com. As long as the IP address from the warning is in the range of IP addresses in the previously mentioned Help page, you shouldn’t be concerned. Specifically, the new addresses that are being added this time are in the range from
220.127.116.11. The warning message looks like this:
Warning: Permanently added the RSA host key for IP address '$IP' to the list of known hosts.
Thanks for your patience and continued support as we work to make GitHub faster and more reliable!