Build what's next on GitHub, the place for anyone from anywhere to build anything.
Join us October 28-29 in San Francisco or online for GitHub Universe, our flagship developer event uniting people, agents, and the world's code.
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…
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 204.232.175.90, in addition to the current IP
(207.97.227.239). 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
address:
This warning is the expected behavior of SSH clients.
Please note that in the near future, we will be adding an additional IP subnet:
192.30.252.0/22 (or as a range, 192.30.252.1 - 192.30.255.255).
