Microsoft’s GitHub Hit by Major Outage as AI-Driven Demand Strains Infrastructure

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

GitHub, the Microsoft Corp.-owned code hosting platform serving more than 180 million developers, is still reeling from a widespread outage on Monday that severely disrupted software development pipelines globally. The hours-long incident was the latest in a relentless series of reliability failures for a service struggling to keep pace with an unprecedented surge in artificial intelligence (AI)-assisted coding traffic. The disruptions began around 9:40 a.m. EDT, initially manifesting as performance degradation across core services. The issue rapidly escalated, causing error rates to spike near 20% for web interface and API traffic, while archive and raw repository content downloads suffered a staggering 50% failure rate. Key capabilities — including GitHub Actions automated testing, webhooks, GitHub Pages, and the AI pair-programmer Copilot — were heavily compromised. Downdetector logged thousands of user reports at the peak of the disruption, with minor outage spikes simultaneously impacting Microsoft Teams. By midday, GitHub engineers reported they had identified the problematic component and deployed corrective action. While incident reports began to subside, the root cause remained undisclosed. The service failure arrives amid growing developer fatigue over GitHub’s operational stability. The platform recorded eight separate degradation incidents in July alone, followed by an Aug. 6 disruption that GitHub itself labeled “unacceptable.” Engineers have pointed to structural bottlenecks as the ecosystem buckles under massive traffic increases. Earlier this year, GitHub …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://devops.com/microsofts-github-hit-by-major-outage-as-ai-driven-demand-strains-infrastructure/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.