What is a key network limitation of GitHub-hosted runners that organizations with strict network policies must address?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Standard GitHub-hosted runners get a different IP each time — so you can't whitelist them by IP in your firewall or external APIs.
Full explanation below image
Full Explanation
Standard GitHub-hosted runners use dynamic IP addresses from GitHub's published CIDR ranges, making IP-based allowlisting impractical for external services. Solutions include: (1) Using GitHub 'larger runners' which can be configured with static IP addresses; (2) Routing traffic through a private network gateway; (3) Using network proxy solutions; (4) Using self-hosted runners that have known, static IPs. GitHub-hosted runners DO have internet access. Private cloud resources can be accessed via VPN tunnels or private network peering. There's no documented 10 Mbps limit — bandwidth is generally adequate for CI workloads.