GitHub Confirms 8-Hour Code Search Outage on April 1, 2026
GitHub suffered a critical 8-hour and 43-minute degradation of its code search service on April 1, 2026, with a 2-hour and 20-minute period of complete unavailability, the company disclosed in its monthly availability report. The outage, caused by an overly aggressive infrastructure upgrade, left 100% of search queries failing during the peak window. A separate incident on the same day temporarily disrupted the audit log service for 28 minutes, though no data was lost.
“We understand how disruptive search outages are for developers who rely on instant code discovery,” said a GitHub spokesperson. “Our immediate focus is on preventing recurrence through stricter deployment safeguards and faster recovery tooling.” The company has since outlined five specific improvements to its infrastructure stability.
Code Search Outage: Timeline and Root Cause
Between 14:40 and 17:00 UTC, GitHub’s code search service was fully unavailable. Service returned in a degraded state at 17:00 UTC with stale results, and full recovery with current data was achieved by 23:45 UTC. During the 2-hour-20-minute full outage, every code search request failed.
The incident began during a routine upgrade to the messaging system that supports code search indexing. An automated change was applied too aggressively, causing coordination failure between internal services. Search indexing halted, and results became stale. While engineers worked to restore messaging, an unintended service deployment erased internal routing state, escalating the staleness into a complete outage.
“We restored coordination through a controlled restart of the messaging infrastructure, then reset the search index to a point before the disruption,” explained the GitHub engineering team in a blog post. “No repository data was lost—the search index is a secondary copy.” Re-indexing finished around midnight UTC, returning accurate results.
Audit Log Service Disruption
On the same day, between 15:34 and 16:02 UTC, GitHub’s audit log service lost connectivity to its backing data store due to a failed credential rotation. During this 28-minute window, audit log history was unavailable via both the API and web UI. A total of 4,297 API actors and 127 github.com users received 5xx errors. Events created during this window were delayed by up to 29 minutes but were ultimately written and streamed without loss.
GitHub Cloud Enterprise customers with data residency were not impacted. The company was alerted six minutes after the failure began, but full service was restored within 28 minutes. “We’ve since hardened the credential rotation process to prevent similar disruptions,” the spokesperson noted.
Background
GitHub experienced a total of 10 incidents in April 2026 that resulted in degraded performance across its services. To increase transparency, the company released a detailed blog post covering the major incidents on April 23 and April 27, and has expanded the GitHub status page with more granular incident data. These steps are part of a broader commitment to reliability.
The company is actively investing in both near-term fixes and long-term architectural improvements. The April 1 incidents underscore the complexity of maintaining a global platform serving millions of developers.
What This Means
For developers and organizations relying on GitHub for code search and audit logging, these outages highlight the fragility of even robust cloud services. The code search outage directly impacted productivity for teams working in large monorepos or exploring unfamiliar codebases. The audit log disruption, while brief, could affect compliance workflows that depend on real-time event streaming.
In response, GitHub is implementing five key changes: gradual upgrades with better health checks to catch problems before they cascade, deployment safeguards to prevent unintended changes during active incidents, faster recovery tooling to reduce time-to-restore, better traffic isolation to prevent cascading impact from unexpected spikes, and hardened credential rotation processes. These measures aim to reduce both the frequency and duration of future outages.
“We appreciate your patience as we work through these investments,” the company stated. “Our goal is to ensure that reliability scales with the trust you place in us.” Developers should monitor the GitHub Status page for real-time updates and post-incident reports.