Incident with Git Operations
Incident
Report for GitHub
Resolved
This incident has been resolved.
From 11:21 to 16:07 UTC some GitHub customers experienced errors cloning via workflows or via the command line.
A third-party configuration change resulted in an unexpected behavior to our systems that resulted in Git clone failures. Once we detected the change we were able to disable it, and our systems started operating normally.
With the incident mitigated, we are working with our third-party provider to improve subsequent configuration change rollouts.
From 11:21 to 16:07 UTC some GitHub customers experienced errors cloning via workflows or via the command line.
A third-party configuration change resulted in an unexpected behavior to our systems that resulted in Git clone failures. Once we detected the change we were able to disable it, and our systems started operating normally.
With the incident mitigated, we are working with our third-party provider to improve subsequent configuration change rollouts.
Update
We have mitigated the cause of the issue and are awaiting positive confirmation from impacted customers that the issue is fully resolved.
Update
We are currently investigating reports from some customers encountering errors when cloning repositories via workflows or via the command line. We do not currently have an ETA for resolution. Next update in 30 minutes.
Investigating
We are investigating reports of degraded performance for Git Operations
This incident affected: Git Operations.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe