April 2026 GitHub Service Incidents: Key Questions and Answers

In April 2026, GitHub faced 10 incidents that affected service performance. Two notable events—the code search outage on April 1 and an audit log service disruption—illustrate the challenges and responses. Below, we answer common questions about these incidents and the steps GitHub is taking to improve transparency and reliability.

1. What happened with GitHub’s code search on April 1, 2026?

On April 1, between 14:40 and 17:00 UTC, GitHub’s code search became fully unavailable—100% of search queries failed. After 2 hours and 20 minutes, service returned in a degraded state, returning stale results that didn’t include repository changes made after 07:00 UTC that day. Full recovery, with current data, was achieved by 23:45 UTC. During the outage, no code search results were accessible. The root cause was a routine infrastructure upgrade that went wrong.

2. What caused the code search outage?

During a routine upgrade to the messaging system supporting code search, an automated change was applied too aggressively, breaking coordination between internal services. This halted search indexing, making results go stale. While the team tried to recover, an unintended service deployment cleared internal routing state, turning the staleness into a complete outage. Fortunately, no Git repository data was lost—only the secondary search index was affected.

3. How was the code search outage resolved?

The team restored the messaging infrastructure through a controlled restart, reestablishing service coordination. They then reset the search index to a point in time before the disruption. As index data was still intact from Git repositories, no data loss occurred. Once re-indexing completed, all search results reflected the latest repository state. Full recovery took until 23:45 UTC, about 9 hours after the initial problem.

4. What measures is GitHub taking to prevent similar incidents?

GitHub is implementing more 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 downtime, and better traffic isolation to limit impact from unexpected spikes. These investments aim to increase system resilience and minimize future disruptions.

5. What happened with the audit log service on April 1?

Between 15:34 and 16:02 UTC, the 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, causing 5xx errors for 4,297 API actors and 127 web users. Events created during the outage were delayed by up to 29 minutes. However, no audit log events were lost—all were eventually written and streamed successfully. Customers with data residency were not impacted.

6. How did GitHub respond to the audit log incident?

GitHub was alerted to the infrastructure failure at 15:40 UTC—six minutes after the first errors. The team quickly identified the credential rotation failure and worked to restore connectivity. The service was fully recovered by 16:02 UTC. To prevent recurrence, GitHub is reviewing its credential management processes and improving alerting for such failures. The incident was fully transparent, with no permanent data loss.

7. How is GitHub improving transparency about incidents?

At the end of April, GitHub published a blog post detailing major incidents from April 23 and 27. They are also enhancing the GitHub status page to provide more granular updates during ongoing issues. By sharing root causes, impacts, and remediation plans, GitHub aims to build trust and help users understand what happened and what’s being done to prevent future problems.