- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 32of 100
What to do
Check whether your product depends on GitHub. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 8h 43m it lasted.
Anything that failed between 2026-04-01 15:02 UTC and 2026-04-01 23:45 UTC may need a replay.Subscribe to GitHub's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from GitHub 7
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- investigating
We identified an issue in our ingestion pipeline that degraded the freshness of Code Search results. While fixing the issue with the ingestion pipeline, a deployment caused a loss of dynamic configuration which is causing most requests for Code Search results to fail. We are working to restore the service and to re-ingest the misaligned data.
provider
- investigating
We are observing some recovery for Code Search queries, but customers should be aware that the data being served may be stale, especially for changes that took place after 07:00 UTC today (1 April 2026). We are still working on recovering our ingestion pipeline, and synchronizing the indexed data. We will update again within 2 hours.
provider
- investigating
We are still working on recovering back to a serviceable state and expect to have a more substantial update within another two hours.
provider
- investigating
We have stabilized Code Search infrastructure, and are in the final stages of validation before slowly reintroducing production traffic.
provider
- investigating
Code search has recovered and is serving production traffic.
provider
- resolved
On April 1st, 2026 between 14:40 and 17:00 UTC the GitHub code search service had an outage which resulted in users being unable to perform searches. The issue was initially caused by an upgrade to the code search Kafka cluster ZooKeeper instances which caused a loss of quorum. This resulted in application-level data inconsistencies which required the index to be reset to a point in time before the loss of quorum occurred. Meanwhile, an accidental deploy resulted in query services losing their shard-to-host mappings, which are typically propagated by Kafka. We remediated the problem by performing rolling restarts in the Kafka cluster, allowing quorum to be reestablished. From there we were able to reset our index to a point in time before the inconsistencies occurred. The team is working on ways to improve our time to respond and mitigate issues relating to Kafka in the future.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d0b0c3fa84
Is GitHub still down?
No, this incident was resolved 2026-04-01 23:45 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
8h 43m, from 2026-04-01 15:02 UTC to 2026-04-01 23:45 UTC, by the times GitHub posted.
What caused it?
GitHub hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.