GitHub Has Had 1,125 Incidents Since 2016 — Is It Cooked?
GitHub Outage Tracker: Is GitHub Cooked?
A new site, isgithubcooked.com, tracks GitHub's incident history, revealing 1,125 incidents since March 2016, with an average of 24 per month. The worst month was February 2026 with 37 incidents, and the longest incident-free streak was just 8 days. Copilot and Actions have the lowest uptime at around 98.2%. The site lets you filter incidents by service and severity to see how outages affect your own stack.
I made this site because I wanted to filter GitHub's incident history for the services and severity levels that affect the products I build.
- kashnote
I think we need to have a little more sympathy for GitHub. You could justify the jabs when we could all blame any outage on the migration to Azure, but then they shared numbers around the scale they're dealing with now that everyone is constantly building and pushing with AI.
I think it's commendable that they're not limiting access to the site or (intentionally) throttling newcomers. Yes, they need to get this figured out, but a little sympathy goes a long way. I personally wish them the best and hope their on-call people can go back to getting normal amounts of sleep soon.
- joshuahedlund
Given that the outages are caused by record traffic, so far they are only cooked in the Yogi Berra sense of “Nobody goes there anymore, it’s too crowded”
- xyst
Now add an rss/atom feed link and you have my support
- Fuzzwah
Near the end of the 8.5 years that I worked at GitHub as an enterprise support engineer, I asked in an all hands if a "GitHub Classic" product had been considered. Much like World of Warcraft Classic, I imagined it would be a rewrite focused on matching the simpler feature set of the past.
I was basically given the same response that blizzard gave that question; "you think you want that but you don't".
- JeremyHerrman
> "GitHub has had 1125 incidents since February 2016, implying a monthly incident rate of 24"
1125 incidents / 126 months ≈ 8.9 incidents per month, not 24
still terrible, but why such an obvious error in the first sentence...
- _heimdall
I feel for the team having to deal with these problems at github today. Its also beyond me how those in charge for years wouldn't have seen this coming.
Github was bought by Microsoft, whether they wanted to acknowledge that internally or not. Microsoft went deep on LLMs, and specifically on LLMs for coding use cases. They must have recognized that LLM generated code and PRs would effectively DDoS GitHub.
I can only assume they simply didn't care, likely driven by greed.
- imnes
It's not making headlines, but Google and Apple seem to be getting hammered by AI as well. Getting app updates approved to release on prod on Play Store / App store used to take days, now it's taking weeks.
- bushbaba
could have been a page with a static 'Yes' and a significant portion of time it'd be accurate.