Breaking: GitHub Reports 10 Service Incidents in April 2026
GitHub experienced ten separate incidents in April 2026 that caused degraded performance across its services, the company announced today. The most severe disruptions occurred on April 1, with a 8-hour code search outage and a 28-minute audit log failure affecting thousands of users.
“We understand how critical reliability is for our users,” said a GitHub spokesperson in a statement. “We are investing in long-term improvements to prevent similar issues.”
Incident Details: Code Search Outage
On April 1, between 14:40 and 17:00 UTC, GitHub’s code search service was fully unavailable, with 100% of queries failing. The root cause was an automated change applied too aggressively during a routine infrastructure upgrade to the messaging system supporting code search.
“This caused a coordination failure between internal services, halting search indexing and eventually leading to a complete outage,” the company explained. After a controlled restart of messaging infrastructure, service was restored in a degraded state by 17:00 UTC, with full recovery by 23:45 UTC. No repository data was lost.
Audit Log Disruption
On the same day, between 15:34 and 16:02 UTC, the audit log service became unavailable due to a failed credential rotation that caused loss of connectivity to its backing data store. During this 28-minute window, 4,297 API actors and 127 github.com users experienced 5xx errors.
“No audit log events were lost,” the company confirmed. “Events created during the window were delayed by up to 29 minutes but ultimately written and streamed successfully.” Customers using GitHub Enterprise Cloud with data residency were not impacted.
Background: Ongoing Reliability Efforts
GitHub has been working to improve transparency and stability. At the end of April, the company released a blog post covering major incidents on April 23 and 27, in addition to the April 1 events. The status page has also been enhanced with more detail.
The company outlined several corrective measures, including gradual upgrades with better health checks, deployment safeguards to prevent unintended changes during active incidents, faster recovery tooling, and better traffic isolation. “These steps are designed to catch problems before they cascade,” the spokesperson said.
What This Means for Users
For developers and organizations relying on GitHub, these outages disrupt workflows and reduce trust in platform availability. The code search outage in particular—lasting over eight hours—can severely impact productivity for teams that depend on quick code discovery.
GitHub’s investments in reliability are crucial, but the frequency of incidents (10 in one month) highlights ongoing challenges. Users should monitor the GitHub status page for real-time updates and consider local backups for critical operations.
- Code Search: Full outage for 2h20m, degraded for 8h43m total.
- Audit Log: 28-minute unavailability with delayed events.
- Other Incidents: The company did not detail all ten but promised improved incident reporting.
GitHub plans to continue near-term and long-term investments. “Thank you for your patience as we work through these improvements,” the spokesperson added.