GitHub's code search service experienced degraded performance for 4.8 hours, with users encountering increased latency and timeout errors. The issue was traced to elevated CPU usage on a single shard within the code search infrastructure. GitHub identified the root cause, implemented a fix to isolate and mitigate the affected shard, and fully resolved the incident.
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
We have identified a cause for the latency and timeouts and have implemented a fix. We are observing initial recovery now.
Customers using code search continue to see increased latency and timeout errors. We are working to mitigate issues on the affected shard.
Elevated latency and timeouts for code search is isolated to a single shard experiencing elevated CPU. We are taking steps to isolate and mitigate the affected shard.
Elevated latency and timeouts for code search is isolated to a single shard experiencing elevated CPU. We are continuing to investigate the cause and steps to mitigate.
We are continuing to investigate elevated latency and timeouts for code search.
We are investigating reports of impacted performance for some GitHub services.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with