<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CAST on Revelara</title><link>https://revelara.ai/tags/cast/</link><description>Recent content in CAST on Revelara</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 26 May 2026 08:00:00 -0700</lastBuildDate><atom:link href="https://revelara.ai/tags/cast/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub's February 9 Incidents: What 'Mitigation' Leaves Out</title><link>https://revelara.ai/blog/mitigation-theater-github-february-9/</link><pubDate>Tue, 26 May 2026 08:00:00 -0700</pubDate><guid>https://revelara.ai/blog/mitigation-theater-github-february-9/</guid><description>&lt;p&gt;GitHub&amp;rsquo;s availability report for February 2026 covers six incidents and there are two on February 9 worth reviewing. Two windows of degraded service an hour and fourteen minutes apart, and GitHub&amp;rsquo;s own investigation found they came from the same underlying cause. The first was declared mitigated before the second began. The mitigation GitHub applied was a correct response to what the team could see at the time. It also was not enough to prevent the second incident.&lt;/p&gt;</description></item></channel></rss>