GitHub logged 10 service incidents last month, according to an availability report the company released Tuesday. The disruptions hit Copilot, search, and other core features, though the company did not specify total downtime or how many users were affected.
The April Incidents
GitHub's April 2026 availability report lists 10 separate incidents spread across the month. While the company didn't break down each outage's duration or root cause in the summary, the report covers problems with Copilot, the AI-powered coding assistant, and GitHub's search functionality. Other services were also impacted, though GitHub hasn't detailed which ones or to what degree.
The report is part of a broader push by the Microsoft-owned platform to be more open about its reliability. GitHub has faced scrutiny in the past over how it communicates outages, and this monthly summary is a direct response to that criticism.
A Transparency Pledge
Alongside the April numbers, GitHub promised to increase transparency around platform stability. The company didn't outline specific metrics or a public dashboard, but the report itself is a step in that direction. For now, the monthly availability summaries are the main channel for users to track performance.
GitHub's move comes as developers grow increasingly reliant on cloud-hosted tools like Copilot. A single outage can stall work for teams that depend on real-time suggestions and collaborative features. Transparency around those disruptions helps users plan around potential downtime.
What’s Next
GitHub hasn't said whether the monthly reports will become permanent or if they'll include more granular data, like incident duration or affected regions. The next report, covering May 2026, is expected in early June. Until then, developers will watch the company's status page and see if the promised transparency turns into a consistent practice.
