GitHub: Incident with Git Operations
Timeline of updates
- 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 GitHub’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitHub, started 2023-10-22 15:16 UTC, resolved after 51 min, 1 update(s).
- Title
- Incident with Git Operations
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/lw4dvwltm025
GitHub profileRecent GitHub incidentsAll outages on October 22, 2023GitHub in October 2023MarkdownJSON