GitHub Status

Resolved: On January 13, 2025, between 23:35 UTC and 00:24 UTC all Git operations were unavailable due to a configuration change causing our internal load balancer to drop requests between services that Git relies upon.

We mitigated the incident by rolling back the configuration change.

We are improving our monitoring and deployment practices to reduce our time to detection and automated mitigation for issues like this in the future.

Investigating: We've identified a cause of degraded git operations, which may affect other GitHub services that rely upon git. We're working to remediate.

Investigating: Actions is experiencing degraded performance. We are continuing to investigate.

Investigating: Pages is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded availability for Git Operations

Resolved: This incident has been resolved.

Investigating: The incident has been resolved, but please note affected pull requests will self repair when any commits are pushed to the pull requests' base branch or head branch. If you encounter problems with a rebase and merge, either click the "update branch" button or push a commit to the PR's branch.

Investigating: We have mitigated the incident, and any new pull request rebase merges should be recovered. We are working on recovery steps for any pull requests that attempted to merge during this incident.

Investigating: We believe to have found a root cause, and in the process of verifying the mitigation.

Investigating: We are still continuing to investigate.

Investigating: We are still experiencing failures for rebase merges in pull requests, we are continuing to investigate.

Investigating: We are investigating reports of degraded performance for Pull Requests

Resolved: On January 13, 2025, between 23:35 UTC and 00:24 UTC all Git operations were unavailable due to a configuration change causing our internal load balancer to drop requests between services that Git relies upon.

We mitigated the incident by rolling back the configuration change.

We are improving our monitoring and deployment practices to reduce our time to detection and automated mitigation for issues like this in the future.

Investigating: We've identified a cause of degraded git operations, which may affect other GitHub services that rely upon git. We're working to remediate.

Investigating: Actions is experiencing degraded performance. We are continuing to investigate.

Investigating: Pages is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded availability for Git Operations

Resolved: On January 13, 2025, between 23:35 UTC and 00:24 UTC all Git operations were unavailable due to a configuration change causing our internal load balancer to drop requests between services that Git relies upon.

We mitigated the incident by rolling back the configuration change.

We are improving our monitoring and deployment practices to reduce our time to detection and automated mitigation for issues like this in the future.

Investigating: We've identified a cause of degraded git operations, which may affect other GitHub services that rely upon git. We're working to remediate.

Investigating: Actions is experiencing degraded performance. We are continuing to investigate.

Investigating: Pages is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded availability for Git Operations

Resolved: This incident has been resolved.

Investigating: We are beginning to see recovery for users connecting to Codespaces. Any users continuing to see impact should attempt a restart.

Investigating: We are investigating reports of timeouts for Codespaces users creating new or connecting to existing Codespaces. We will continue to keep users updated on progress towards mitigation.

Investigating: We are investigating reports of degraded performance for Codespaces