Creează un cont pentru a te abona la acest blog și a-i urmări articolele pe pagina Lectură.
-
The other day, I wrote about a GitHub Actions incident.
-
Last week, GitHub Actions experienced another incident.
-
I’m using this post to gather together some common threads I’ve noticed after reading write-ups of major cloud software incidents.
-
Recently, two AI-related pieces of content caught my attention.
-
In yesterday’s post about the recent GitHub outage, there was a detail in the writeup that I didn’t say anything about: the autoscaling policy on the service with the saturated Istio sidecar.
-
It wasn’t even a week ago when I wrote about a major GitHub incident.
-
The folks at Microsoft Azure recently wrote up a post incident review for a networking issue in their West U.S region.
-
On August 6, 2026, GitHub had a pretty rough incident: GitHub Actions was degraded for about nine hours.
-
As a fan of resilience engineering, I often differ with people on where we should focus our scarce engineering cycles in order to improve reliability.
-
There’s a new software reliability conference that just spun up called Software Should Work, and I had a chance to give a talk there.