We’re introducing calendar-based versioning for our REST API, so we can keep evolving our API, whilst still giving integrators a smooth migration path and plenty of time to update their integrations.
As we expand our infrastructure, we are making changes to the
IP addresses currently in use.
If you are explicitly whitelisting GitHub in your firewall rules,
please make sure that you include all of the IP ranges
as described in this article.
Soon, we will begin using additional IP addresses (A records) for GitHub.com in order to add more load balancers.
Starting Thursday, April 4, 2013, GitHub.com will also resolve to
184.108.40.206, in addition to the current IP
220.127.116.11). Both addresses resolve to GitHub.com via reverse DNS.
If you are using SSH, you will see this message the first time you see this IP
Warning: Permanently added the RSA host key for IP address '18.104.22.168' to the list of known hosts.
This warning is the expected behavior of SSH clients.
Please note that in the near future, we will be adding an additional IP subnet:
22.214.171.124/22 (or as a range,
126.96.36.199 - 188.8.131.52).