<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Gcp on Azarudeen.com</title><link>https://azarudeen.com/tags/gcp/</link><description>Recent content in Gcp on Azarudeen.com</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 06 Aug 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://azarudeen.com/tags/gcp/index.xml" rel="self" type="application/rss+xml"/><item><title>Agents On Call: DNS Races, Feature Files, and the AI-Assisted Postmortem</title><link>https://azarudeen.com/posts/11-jul-2025-to-present-agents-on-call/</link><pubDate>Thu, 06 Aug 2026 10:00:00 +0530</pubDate><guid>https://azarudeen.com/posts/11-jul-2025-to-present-agents-on-call/</guid><description>&lt;h1 id="agents-on-call-jul-2025--aug-2026"&gt;Agents On Call (Jul 2025 – Aug 2026)&lt;/h1&gt;
&lt;p&gt;This window opened with a dormant config error and got worse from there. AWS,
Azure, and Cloudflare each had a headline global outage within a single month of
autumn 2025, and &amp;ldquo;the internet is three companies in a trench coat&amp;rdquo; became a
mainstream joke. A year later, July 2026 delivered four provider incidents in
nine days. Underneath all of it, the biggest shift since the SRE book has been
quietly happening: AI agents moving from summarizing incidents to actually
responding to them.&lt;/p&gt;</description></item></channel></rss>