## Description Approximately 1-2% of infrastructure-related failures show "fatal: the remote end hung up unexpectedly", indicating a network connection issue during Git operations. ## Affected Jobs Below are some examples of JobID and its respective Correlation ID | Job ID | correlation ID | | ------ | ------ | | [Job #10062840858](https://gitlab.com/gitlab-org/gitlab/-/jobs/10062840858) | 796de6311332695f6e7386c679dd2c00 | | | | ## Error Logs ``` git push -f "${FOSS_REPOSITORY}" "${AS_IF_FOSS_BRANCH}" error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502 send-pack: unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly ``` ## Preliminary Analysis This error occurs when a network connection is unexpectedly terminated during a Git operation. Common causes include: - Network timeouts (operation took too long) - Runner network stability issues Notably, there were [no reported incidents]([no Incident](https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7)) on the GitLab status page on the days when these failures occurred, suggesting this is not part of a broader service disruption. ## Next Steps - Connect with the team handling Runners , and git operation - Implement retry logic