# GitHub: Incident with Git Operations, API Requests, Actions, Pages, Issues and Copilot

- Impact (vendor’s label): major
- Status: resolved
- Started: 2024-04-10 18:41 UTC · Resolved: 2024-04-10 19:03 UTC · Duration: 22 min
- Updates: 1
- [Vendor status page: https://www.githubstatus.com/incidents/9zq8p50p7tkh](https://www.githubstatus.com/incidents/9zq8p50p7tkh)
- [Company: GitHub](https://rewindex.com/company/github.md)

## Timeline of updates

- **resolved** 2024-04-10 19:03 UTC: On April 10, 2024, between 2024-04-10 18:33 UTC and 2024-04-10 19:03 UTC, several services were degraded due to the release of a compute-intensive database query that prevented a key database cluster from serving other queries. GitHub Actions saw delays and failures across the entire run life cycle and had a significant increase in the number of timeouts in API requests. All Pages deployments failed for the duration of the incident. Git Systems saw approximately 12% of raw file download requests and 16% of repository archive download requests return HTTP 50X error codes for the duration of the incident. Issues experienced increased latency for issue creation and updates. Codespaces saw roughly 500 requests to create and resume a Codespace timeout during the incident. We mitigated the incident by rolling back the offending query. We are working to introduce measures to automatically detect compute-intensive queries in test runs during CI to prevent an issue like this one from recurring.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/github/incidents/9zq8p50p7tkh · Markdown: https://rewindex.com/company/github/incidents/9zq8p50p7tkh.md · JSON: https://rewindex.com/api/v1/companies/github/incidents/9zq8p50p7tkh · Generated 2026-10-18T09:34:59.746Z