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

Racing into 2025 with new GitHub Innovation Graph data
Discover the latest trends and insights on public software development activity on GitHub with the quarterly release of data for the Innovation Graph, updated through December 2024.

GitHub Availability Report: March 2025
In March, we experienced one incident that resulted in degraded performance across GitHub services.

Vibe coding with GitHub Copilot: Agent mode and MCP support rolling out to all VS Code users
In celebration of MSFT’s 50th anniversary, we’re rolling out Agent Mode with MCP support to all VS Code users. We are also announcing the new GitHub Copilot Pro+ plan w/ premium requests, the general availability of models from Anthropic, Google, and OpenAI, next edit suggestions for code completions & the Copilot code review agent.