GitHub: Incident with GIT LFS and Other Requests
Timeline of updates
- resolved
On February 6, 2025, between 8:40AM UTC and 11:13AM UTC the GitHub REST API was degraded following the rollout of a new feature. The feature resulted in an increase in requests that saturated a cache and led to cascading failures in unrelated services. The error rate peaked at 100% of requests to the service. The incident was mitigated by increasing the allocated memory to the cache and rolling back the feature that led to the cache saturation. To prevent future incidents, we are working to reduce the time to detect a similar issue and optimize the overall calls to the cache.
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 2025-02-06 09:42 UTC, resolved after 1.5 h, 1 update(s).
- Title
- Incident with GIT LFS and Other Requests
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/yhn3m0yqdxmc
GitHub profileRecent GitHub incidentsAll outages on February 6, 2025GitHub in February 2025MarkdownJSON