James Ding
Aug 13, 2025 21:33
GitHub experienced a service disruption in July 2025 due to an infrastructure issue impacting the GitHub Enterprise Importer. The incident led to degraded performance across services.
In July 2025, GitHub encountered a significant service disruption, according to the GitHub Availability Report. The incident, which occurred on July 28, resulted in degraded performance across GitHub services, affecting users globally.
Details of the Incident
The disruption began at approximately 21:41 UTC on July 28 and lasted for over five hours, until 03:15 UTC on July 29. The issue was traced to the GitHub Enterprise Importer (GEI), which entered a degraded state. During this period, migrations could not be processed, causing inconvenience to users relying on these services.
The root cause of the problem was identified as a component of the GEI infrastructure that had been inadvertently taken out of service during routine internal improvements. This action led to a failure in restoring the infrastructure to its previous configuration, necessitating the deployment of new resources to resolve the issue.
Measures and Improvements
In response to the incident, GitHub has implemented several improvements aimed at enhancing recovery capabilities, unit testing, and validation using test data. These measures are intended to prevent similar incidents in the future and improve the overall resilience of GitHub services.
Changes in IP Allow Lists
As part of the recovery process, GitHub announced changes to its IP allow lists. Customers are required to add new IP ranges to their allow lists, including:
- 20.99.172.64/28
- 135.234.59.224/28
Additionally, the following IP ranges are no longer in use and can be removed from all applicable allow lists:
- 40.71.233.224/28
- 20.125.12.8/29
Communication with Users
GitHub has proactively reached out to users who have utilized the GitHub Enterprise Importer in the past 90 days, alerting them to these changes. Users are encouraged to contact Customer Support for any migration-related issues.
For ongoing updates and further details about service status, users can visit the GitHub status page. Additionally, insights into GitHub’s ongoing engineering efforts can be found on the GitHub Engineering Blog.
Image source: Shutterstock
Credit: Source link
