Overview
In April 2026, GitHub experienced ten incidents that temporarily degraded performance across its services. This article provides a detailed review of the most significant events, the root causes behind them, and the steps GitHub is taking to enhance system resilience. For full transparency, GitHub also published a dedicated blog post covering major incidents on April 23 and April 27, and has updated its status page with more granular information.
Incident Analysis: Code Search Outage (April 1, 2026)
On April 1, between 14:40 and 17:00 UTC, GitHub’s code search service was completely unavailable. During this 2-hour and 20-minute window, 100% of search queries failed. The service was partially restored by 17:00 UTC, but results were temporarily stale—reflecting repository data only up to approximately 07:00 UTC that day. Full recovery, with current data, was achieved by 23:45 UTC. The total duration of degraded performance was 8 hours and 43 minutes.
Root Cause
During a routine infrastructure upgrade to the messaging system that supports code search, an automated change was applied too aggressively. This caused a coordination failure among internal services, halting search indexing and causing results to become stale. While the engineering team worked to recover the messaging infrastructure, an unintended service deployment cleared internal routing state, escalating the staleness issue into a complete outage.
Resolution and Impact
The messaging infrastructure was restored via a controlled restart, reestablishing coordination between services. The search index was then reset to a point in time before the disruption. No repository data was lost—the search index is a secondary index derived from Git repositories, which were completely unaffected. Once re-indexing completed, all search results reflected the current state of repositories.
Preventive Measures
- 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 service.
- Better traffic isolation to prevent cascading impact from unexpected traffic spikes during outages.
Incident Analysis: Audit Log Service Disruption (April 1, 2026)
Later 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 the web UI, resulting in 5xx errors for 4,297 API actors and 127 github.com users. Furthermore, events created during this window were delayed by up to 29 minutes in github.com and event streaming. No audit log events were lost; all were ultimately written and streamed successfully. Customers using GitHub Enterprise Cloud with data residency were not impacted.
Response Time
The infrastructure failure triggered alerts at 15:40 UTC—six minutes after the incident began. The team immediately initiated remediation.
Lessons Learned
This incident highlights the importance of robust credential rotation procedures and rapid detection of data store connectivity issues. GitHub is reviewing its credential management processes to prevent similar failures in the future.
Additional Incidents and System Improvements
Beyond the April 1 events, GitHub experienced eight other incidents during the month, including two major ones on April 23 and April 27. The engineering organization has emphasized near-term and long-term investments to improve overall reliability. These include enhanced monitoring, better incident response playbooks, and ongoing infrastructure hardening.
Conclusion
GitHub’s transparency around these incidents helps build trust with its user community. While April 2026 saw a higher-than-usual number of disruptions, the company’s commitment to sharing detailed root causes and corrective actions demonstrates a proactive approach to system reliability. Users can expect continued improvements as GitHub implements the preventive measures outlined above.
For real-time status updates, refer to the GitHub Status Page. For more details on the April 23 and April 27 incidents, see the companion blog post.