IP Blacklisting Issues Impacting GitHub Access

[aashinuday]

Select Topic Area

Question

GitHub Feature Area

Pull Requests

Body

We are a neo cloud provider based in India, serving a growing set of customers who heavily rely on GitHub for their development workflows. However, we've been facing recurring issues where our public IP blocks are being blacklisted, leading to disruptions in upload/download activities and, in many cases, bringing our customers' production workloads to a complete halt.

This has become a serious concern as it directly impacts our service quality. Our customers have highlighted that they haven’t encountered similar issues on platforms like AWS, Azure, GCP, or even Nebius. We would sincerely appreciate your guidance on the following:

• Is there a process or best practice to ensure our IP ranges are whitelisted or trusted?
• Are there specific terms, licensing, or a CSO (Customer Security Operations) agreement that we should consider to avoid these disruptions?
• Is there a way to proactively coordinate with GitHub to ensure uninterrupted access for our customers?

We are committed to complying with all necessary guidelines and would appreciate your support in resolving this issue in the long term. Looking forward to your advice and assistance.

[queenofcorgis]

Hey there! 👋

Thanks for posting in the GitHub Community, @aashinuday ! We're happy you're here. You are more likely to get a useful response if you are posting in the applicable category. The Accessibility category is a place for our community to discuss and provide feedback on the digital accessibility of GitHub products. Digital accessibility means that GitHub tools, and technologies, are designed and developed so that people with disabilities can use them.

I've gone ahead and moved this to the correct category for you, Repositories. Good luck!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬