Home / News & insights / Company news

GitHub Availability Report: July 2025

In July, we experienced one incident that resulted in degraded performance across GitHub services.

·@jakuboleksy
| 2 minutes

In July, we experienced one incident that resulted in degraded performance across GitHub services.

July 28 21:41 UTC (lasting 5 hours and 34 minutes)

Between approximately 21:41 UTC on July 28, 2025, and 03:15 UTC on July 29, 2025, GitHub Enterprise Importer (GEI) operated in a degraded state where migrations could not be processed. Our investigation found that a component of the GEI infrastructure had been improperly taken out of service during implementation of routine internal improvements, and it could not be restored to its previous configuration. This necessitated the provisioning of new resources to resolve the incident. We have identified and implemented improvements around enabling the recovery of infrastructure, unit testing, and better validation using test data.

As a result, customers will need to add our new IP range to the following IP allow lists, if enabled:

  • The IP allow list on your destination github.com organization or enterprise
  • If you’re running migrations from github.com, the IP allow list on your source github.com organization or enterprise
  • If you’re running migrations from a GitHub Enterprise Server, Bitbucket Server or Bitbucket Data Center instance, the allow list on your configured Azure Blob Storage or Amazon S3 storage account
  • If you’re running migrations from Azure DevOps, the allow list on your Azure DevOps organization

The new GEI IP ranges for inclusion in applicable IP allow lists are:

  • 20.99.172.64/28
  • 135.234.59.224/28

The following IP ranges are no longer used by GEI and can be removed from all applicable IP allow lists:

  • 40.71.233.224/28
  • 20.125.12.8/29

Users who have run migrations using GitHub Enterprise Importer in the past 90 days have received email alerts about this change. Please contact Customer Support for any migration related issues.

Please follow our status page for real-time updates on status changes and post-incident recaps. To learn more about what we’re working on, check out the GitHub Engineering Blog.

Tags:

Written by

Related posts