GitHub Battles 10 Incidents in April, Major Search Outage and Audit Log Failure Among Worst

Breaking: GitHub Reports 10 Service Incidents in April 2026

GitHub experienced ten separate incidents in April that degraded performance across its services, the company disclosed today. The most severe disruptions included an hours-long code search failure and a credential-related audit log outage.

GitHub Battles 10 Incidents in April, Major Search Outage and Audit Log Failure Among Worst — Source: github.blog

Search Service Crippled for Nearly 9 Hours

On April 1, GitHub's code search service went completely dark for 2 hours and 20 minutes, from 14:40 to 17:00 UTC. During that window, 100% of search queries failed. Service returned in a degraded state with stale results until full recovery at 23:45 UTC — a total disruption lasting 8 hours and 43 minutes.

"A routine infrastructure upgrade to the messaging system powering code search was applied too aggressively," a GitHub engineering spokesperson said. "This caused a coordination failure, halting search indexing. An unintended deployment then cleared internal routing, escalating the problem from stale results to a complete outage."

The team restored the messaging infrastructure via a controlled restart and reset the search index to a point before the failure. No repository data was lost — the search index is a secondary copy derived from unaffected Git repositories.

Audit Log Unavailable for 28 Minutes

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 completely unavailable via both API and web UI. The outage affected 4,297 API actors and 127 github.com users, all receiving 5xx errors.

Events created during the outage were delayed by up to 29 minutes. "No audit log events were lost — all were ultimately written and streamed successfully," the spokesperson confirmed. Customers using GitHub Enterprise Cloud with data residency were not impacted.

Additional Incidents and Transparency Push

Beyond the April 1 failures, two major incidents occurred on April 23 and April 27. The company released a dedicated blog post detailing those disruptions and has committed to providing more granular information on the GitHub status page going forward. "Thank you for your patience as we work through near-term and long-term investments we’re making," the company said.

Background

GitHub, the world's largest code hosting platform, processes millions of requests per day. Reliability incidents, while relatively rare, can have outsized impact on software development teams worldwide who depend on the platform for collaboration and CI/CD.

The April incidents follow a pattern of periodic infrastructure upgrades that have previously caused cascading failures. GitHub has been investing in more resilient deployment practices and faster recovery tooling.

What This Means

For developers and enterprises reliant on GitHub, the code search outage meant hours of lost productivity — especially for teams using search to locate code, review changes, or onboard new members. The audit log failure created blind spots for security monitoring and compliance operations.

GitHub has outlined specific remediation steps: gradual upgrades with better health checks to catch problems before they cascade, deployment safeguards to prevent unintended changes during active incidents, faster recovery tooling, and improved traffic isolation to prevent cascading impact from unexpected spikes. These changes aim to reduce both the frequency and severity of future incidents.

However, trust in cloud services is hard to rebuild. Users will be closely watching whether GitHub's promised investments translate into measurable uptime improvements in the coming months.