GitHub BlogJun 11, 2026, 9:30 PMNatalie Guevara

GitHub Availability Report: May 2026

Original: GitHub availability report: May 2026

GitHub reported nine May incidents, including Actions, pull request, Copilot, database, and upstream GPT model disruptions.

GitHub’s May 2026 availability report details nine incidents that degraded core services across github.com, GitHub Actions, pull requests, and GitHub Copilot. The report ties broader reliability pressure to rapidly growing traffic from AI-assisted and agentic development workflows. GitHub says it is shifting more traffic to Azure, isolating major services, improving database safeguards, and strengthening failover for affected Copilot model routes.

GitHub’s May 2026 availability report summarizes nine incidents that caused degraded performance across GitHub services, while also giving a broader update on the company’s reliability work. GitHub says traffic is growing rapidly, driven in large part by AI-assisted and agentic development workflows, and that it is reshaping infrastructure to handle that growth. The company reports that 40% of monolith traffic is now served from Azure, up from 8% in February, with Git traffic at 30% and repository replication at 99%. It says effective capacity has more than doubled in four months. GitHub is also isolating the primary database cluster into independent domains for users, authentication, and authorization, with a new users service fully cut over and stateless authentication tokens rolling out to reduce per-request database lookups.

Full summary

Free shows the 3-line summary; Pro unlocks the full deep summary (~300 words) so you never have to click through.

See Pro plans →

Want the original English / full article?

Read on GitHub Blog →

Summaries are AI-generated; the original article is authoritative.