FT Reveals Kiro AI Triggered 13-Hour AWS Cost Tool Outage; Amazon Calls It User Error

Silicon Valley has seen autonomous software go awry before—Knight Capital’s 1 Aug 2012 algorithmic trading bug vaporized US$440 million in 45 minutes after code was deployed without proper safeguards. The Kiro incident echoes that pattern: cost-cutting drives firms to delegate increasingly privileged tasks to machines while relaxing traditional peer-review gates. Over the past decade, vast swaths of the internet have concentrated onto a handful of hyperscale clouds; a single mis-step inside AWS now reverberates across thousands of organisations, much as AT&T’s 1990 long-distance switch failure cascaded through US phone networks. Whether Amazon’s spin (“user error”) sticks or not, the episode underscores a longer 100-year arc toward code that writes and executes itself—raising existential questions of governance, liability and resilience when the same automation that boosts efficiency also introduces opaque systemic risk.