Do major software firms have more downtime now vs pre‑LLM?

Automatically generated software, especially code produced by Large Language Models (LLMs), is increasingly adopted to accelerate development and reduce manual effort. However, little is known about the long-term reliability of such systems under sustained execution.

Over the twelve months from May 2025 to April 2026, an independent monitor recorded 257 incidents at GitHub, of which 48 were classified as major outages, accounting for a combined 112 h and 18 min of major-outage downtime; across all tracked ...

We're a good year+ into the use LLMs for all major bits of software that we all rely upon and GitHub here is down to one 9 of uptime. I've been using GitHub for a _long_ time, my first commits there go back to August 2009!, and I honestly don't recall GitHub going down as much as it has in ...

Maybe that's just the date when they started tracking uptime using this sytem · I've seen so many times where Company A will complain that their vendors aren't accurate enough about uptime and how Company A notices first that their vendors are down, but then they themselves have a very laggy ...

While AI has come to replace SaaS as a shorthand, the technology delivery model SaaS was primarily meant to convey remains just as prevalent in the LLM era—even if other attributes typically associated with SaaS (such as heavy UI or seat-based subscriptions) are receding.

GitHub's downtime is the result of multiple factors, the primary ones being the following. 2024: There was a 59% surge in the number of contributions to generative AI projects, with total projects being 518 million, according to the Octoverse ...

Secondarily because at some point they had a quite good real-time UI that is slowly sucking more and more (while they seem to be adopting web development practices I dislike). ... i wonder how much llms have increased the load on github, both from the direct copilot integration and from the sheer volume of increased activity by llm agents.

On premises servers handling software repositories and artifactories, heavily locked down, use open source LLM's etc. ... If we're talking about big enterprise, they don't care that much about cost when it's a question of ensuring uptime (and therefore productivity). Cost is a one-time hit that can even be amortized. Downtime is a recurring cost that brings nothing to the table and halts productivity.

Microslop had certainly been investing heavily around GitHub. Specifically in nailing copilot buttons to anything that works. Today pull requests are down - literally the reason to use GitHub. They even transferred it to their Copilot division. Blaming external use of LLM autocoders is disingenuous at best.