Upcoming IP address changes
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.
Additional IP for GitHub.com
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:
Warning: Permanently added the RSA host key for IP address '204.232.175.90' 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:
192.30.252.0/22 (or as a range, 192.30.252.1 - 192.30.255.255).
Written by
Related posts
The developer role is evolving. Here’s how to stay ahead.
AI is changing how software gets built. Explore the skills you need to keep up and stand out.
How GitHub protects developers from copyright enforcement overreach
Why the U.S. Supreme Court case Cox v. Sony matters for developers and sharing updates to our Transparency Center and Acceptable Use Policies.
GitHub Copilot gets smarter at finding your code: Inside our new embedding model
Learn about a new Copilot embedding model that makes code search in VS Code faster, lighter on memory, and far more accurate.