AI load breaks GitHub – why not other vendors?
GitHub has faced significant reliability issues recently, with its uptime dropping to alarming levels. A data integrity incident last month resulted in the loss of commits for over 2,000 pull requests, leaving affected customers to recover their work manually. Additionally, ongoing outages and a critical security vulnerability have led some users, including prominent developers, to abandon the platform in frustration.
- ▪GitHub's reliability fell to 86% this month, with a major data integrity incident affecting over 2,000 pull requests.
- ▪Customers had to manually recover lost commits due to a bug introduced by GitHub during a squash merge process.
- ▪A critical security issue was disclosed, allowing unauthorized access to repositories, which GitHub fixed within six hours.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,301 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | The Pragmatic Engineer |
| Canonical URL | https://blog.pragmaticengineer.com/the-pulse-ai-load-breaks-github/ |
| Publication time | Mon, 25 May 2026 12:59:21 +0000 |
| Retrieval time | 2026-05-25T13:07:37.303Z |
| Last seen | 2026-05-25T13:07:37.303Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | dgG0ROdQEgvl |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
The Pulse: AI load breaks GitHub – why not other vendors? Hi, this is Gergely with a bonus, free issue of the Pragmatic Engineer Newsletter. In every issue, I cover Big Tech and startups through the lens of senior engineers and engineering leaders. Today, we cover one out of four topics from last week’s The Pulse issue. Full subscribers received the article below seven days ago. If you’ve been forwarded this email, you can subscribe here.GitHub’s reliability has been beyond unacceptable recently: last month, third party measurements pinned it at one nine (right at 90%).
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The Pragmatic Engineer.
Discussion
0 commentsMore from The Pragmatic Engineer
