GitHub Reports Severe Service Degradation: Code Search Fully Down for Over Two Hours
GitHub experienced a total of 10 incidents in April 2026 that caused degraded performance across its services, with the most severe being a complete outage of its code search feature on April 1. That incident left 100% of search queries failing for two hours and 20 minutes, according to the company’s monthly availability report released today.
“During a routine infrastructure upgrade to the messaging system supporting code search, an automated change was applied too aggressively, causing a coordination failure between internal services,” a GitHub spokesperson explained. The issue escalated into a full outage after an unintended service deployment cleared internal routing state.
Full recovery took until 23:45 UTC, nearly 10 hours after the initial disruption. No repository data was lost, as the search index is a secondary cache derived from Git repositories.
Background
GitHub has been investing in near-term and long-term improvements to its infrastructure, as outlined in a blog post published at the end of April. The post detailed the two major incidents on April 23 and April 27, but the April 1 incidents—code search and a separate audit log failure—were the most disruptive early in the month.
The audit log service lost connectivity to its backing data store for 28 minutes on April 1 due to a failed credential rotation. During that window, audit log history was unavailable via API and web UI, and 4,297 API actors and 127 github.com users received 5xx errors. However, no events were lost, and all data was eventually written and streamed.
GitHub also added more detail to its status page following the incidents, aiming to provide more granular visibility into ongoing issues.
What This Means
For developers and teams relying on GitHub’s code search and audit logs, these outages highlight the fragility of even the most robust cloud platforms. The code search failure, in particular, could disrupt productivity for those who depend on quick code navigation and reuse.
GitHub has outlined preventive measures: more gradual upgrades with health checks, deployment safeguards to prevent unintended changes during active incidents, faster recovery tooling, and better traffic isolation. “We are committed to reducing the risk and impact of such events in the future,” the spokesperson added.
Customers using GitHub Enterprise Cloud with data residency were not impacted by the audit log incident, but all other users faced some level of service degradation. The company continues to recommend monitoring the status page for real-time updates.
Key Incidents in April 2026
- April 1, 14:40–17:00 UTC: Code search fully unavailable (2h 20m), then degraded until 23:45 UTC.
- April 1, 15:34–16:02 UTC: Audit log service offline (28 min) due to credential rotation failure.
- April 23 and April 27: Major incidents covered in a separate blog post.
- Six additional minor incidents caused degraded performance.
GitHub’s engineering teams are actively implementing the safeguards mentioned above. The company thanks users for their patience as these improvements roll out.