<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cloud Outages on 67AI Lab</title>
    <link>https://67ailab.com/tags/cloud-outages/</link>
    <description>Recent content in Cloud Outages on 67AI Lab</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 11 Sep 2026 09:00:00 +0000</lastBuildDate>
    <atom:link href="https://67ailab.com/tags/cloud-outages/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reliability Horizon 2026: Three Currents Reshaping Site Reliability</title>
      <link>https://67ailab.com/posts/reliability-horizon-2026/</link>
      <pubDate>Fri, 11 Sep 2026 09:00:00 +0000</pubDate>
      <guid>https://67ailab.com/posts/reliability-horizon-2026/</guid>
      <description>&lt;p&gt;Eighteen months ago, &amp;ldquo;AI SRE&amp;rdquo; meant a chatbot next to your dashboard. In September 2026 it means a GA product with an RBAC scope, a per-tool allow/ask/deny policy, and an audit trail. That is a different conversation, and it is worth taking stock of where the field actually stands rather than where the launch posts say it does.&lt;/p&gt;&#xA;&lt;p&gt;This post reads three currents together, from a cloud provider&amp;rsquo;s seat: agents moving from suggesting to acting, reliability being pulled forward out of the pager and into design and verification, and the long tail of outages that neither of those has yet touched. Every figure below is sourced and dated between June 2025 and August 2026.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
