Disruption with Pull Request Ref Updates
Incident
Report for GitHub
Resolved
On April 30, 2025, between 8:02 UTC and 9:05 UTC, the Pull Requests service was degraded and failed to update refs for repositories with higher traffic. This was due to a repository migration creating a larger than usual number of enqueued jobs. This resulted in an increase in job failures, delays for non-migration sourced jobs, and delays to tracking refs.
We declared an incident once we confirmed that this issue was not isolated to the migrating repository and other repositories were also failing to process ref updates.
We mitigated the incident by shifting the migration jobs to a different job queue.
To avoid problems like this in the future, we are revisiting our repository migration process and are working to isolate potentially problematic migration workloads from non-migration workloads.
We declared an incident once we confirmed that this issue was not isolated to the migrating repository and other repositories were also failing to process ref updates.
We mitigated the incident by shifting the migration jobs to a different job queue.
To avoid problems like this in the future, we are revisiting our repository migration process and are working to isolate potentially problematic migration workloads from non-migration workloads.
Update
Some customers of github.com are reporting issues with PR tracking refs not being updated due to processing delays and increased failure rates. We're investigating the source of the issue.
Investigating
We are investigating reports of degraded performance for Pull Requests
This incident affected: Pull Requests.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe