GitHub: Repository searches not working for some users
Timeline of updates
- resolved
On November 21, 2024, between 14:30 UTC and 15:53 UTC search services at GitHub were degraded and CPU load on some nodes hit 100%. On average, the error rate was 22 requests/second and peaked at 83 requests/second. During this incident Enterprise Profile pages were slow to load and searches may have returned low quality results. The CPU load was mitigated by redeploying portions of our web infrastructure. We are still working to identify the cause of the increase in CPU usage and are improving our observability tooling to better expose the cause of an incident like this in the future.
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 2024-11-21 15:30 UTC, resolved after 1.3 h, 1 update(s).
- Title
- Repository searches not working for some users
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/dnq4lp93t62f
GitHub profileRecent GitHub incidentsAll outages on November 21, 2024GitHub in November 2024MarkdownJSON