<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incident on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/incident/</link><description>Recent content in Incident on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 21 Jul 2026 12:20:39 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/incident/index.xml" rel="self" type="application/rss+xml"/><item><title>Knightmare: A DevOps Cautionary Tale (2014)</title><link>https://curadevops.metacog.co.kr/insights/2026-07-21-knightmare-a-devops-cautionary-tale-2014/</link><pubDate>Tue, 21 Jul 2026 12:20:39 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-21-knightmare-a-devops-cautionary-tale-2014/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> The 2012 Knight Capital incident remains a canonical case study on the dangers of inconsistent deployment across nodes and untested code paths — useful for grounding release-safety practices and deployment checklists.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A well-known cautionary tale about how a botched deployment caused $440M in losses in 45 minutes; useful context when making the case for deployment safeguards, progressive delivery, and automated rollback standards.&lt;/li>
&lt;/ul></description></item></channel></rss>