How Cloud Service Disruptions Are Making Resilience Critical for Developers

Cloud-based dev pipelines and AI-enabled coding tools are increasingly exposed to outages that can ripple across development teams, with recent incidents showing that even partial cloud disruptions can halt progress. For example, Anthropic’s Claude[.]ai and Console services suffered a system-wide outage lasting about 30 minutes on 10 September, while July saw GitHub report degraded performance across API, Issues, GraphQL and Pull Requests, with about 4% of requests failing.

Industry voices caution that such events are more often performance hits than full outages, though experts warn a major incident could still cause hours to days of downtime, given the growing reliance on cloud infrastructure, according to Daria Kulikova of GitProtect[.]io.

In the broader landscape, first-half 2025 data show Azure DevOps with 74 incidents and a longest degradation of 159 hours, GitHub incidents up 58% year over year with 109 reported cases, 17 of which were major, and GitLab reporting 59 incidents totalling 1,346 hours of disruption, per GitProtect[.]ai and IsDown’s 2024 Outage Report.

The piece argues resilience should be baked into workflows through local-first approaches, fallbacks and redundancies, to mitigate a systemic single point of failure in modern software development. according to GitProtect[.]ai