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
Pick your agent: Use Claude and Codex on Agent HQ
Claude by Anthropic and OpenAI Codex are now available in public preview on GitHub and VS Code with a Copilot Pro+ or Copilot Enterprise subscription. Here’s what you need to know and how to get started today.
What the fastest-growing tools reveal about how software is being built
What languages are growing fastest, and why? What about the projects that people are interested in the most? Where are new developers cutting their teeth? Let’s take a look at Octoverse data to find out.
Year recap and future goals for the GitHub Innovation Graph
Discover the latest trends and insights on public software development activity on GitHub with data from the Innovation Graph through Q3 2025.