• Azure Front Door: Please Use the Side Entrance – el -jb
• Azure and NVIDIA: A Match Made in GPU Heaven – mk
• Azure Goes Down Under the Weight of Its Own Configuration – el
• GitHub Turns Your Copilot Subscription Into an All-You-Can-Eat Agent Buffet – mk, el
• Microsoft Goes Full Blackwell: No Regrets, Just GPUs
• Jules Verne Would Be Proud: Google’s CLI Goes 20,000 Bugs Under the Codebase
• RAG to Riches: AWS Makes Retrieval Augmented Generation Turnkey
• Kubectl Gets a Gemini Twin: Google Teaches AI to Speak Kubernetes
• I’m Not a Robot: Azure WAF Finally Learns to Ask the Important Questions
• OpenAI Puts 38 Billion Eggs in Amazon’s Basket: Multi-Cloud Gets Complicated
• The Root Cause They’ll Never Root Out: Why Attrition Stays Off the RCA
• Google’s New Extension Lets You Deploy Kubernetes by Just Asking Nicely
• Cursor 2.0: Now With More Agents Than a Hollywood Talent Agency

04:46 Massive Azure outage is over, but problems linger – here’s what happened | ZDNET

• Azure experienced a global outage on October 29, affecting all regions simultaneously, unlike the recent AWS outage that was limited to a single region.
• The incident lasted approximately eight hours from noon to 8 PM ET, impacting major services including Microsoft 365, Teams, Xbox Live, and critical infrastructure for Alaska Airlines, Vodafone UK, and Heathrow Airport, among others.
• The root cause was an inadvertent tenant configuration change in Azure Front Door that bypassed safety validations due to a software defect. Microsoft’s protection mechanisms failed to catch the erroneous deployment, allowing invalid configurations to propagate across the global fleet and cause HTTP timeouts, server errors, and elevated packet loss at network edges.
• Recovery required rolling back to the last known good configuration and gradually rebalancing traffic across nodes to prevent overload conditions.
• Some customers experienced lingering issues even after the official recovery time, with Microsoft temporarily blocking configuration changes to Azure Front Door while completing the restoration process.
• The incident highlights concentration risk in cloud infrastructure, as this marks the second major cloud provider outage in October 2025.
• Despite Azure revenue growing 40 percent in the latest quarterly report, Microsoft’s stock declined in after-hours trading as the company acknowledged capaci...

• CloudWatch’s New Feature: Because Nobody Likes Writing Incident Reports at 3 AM
• DNS: Did Not Survive – The Great US-EAST-1 Outage of 2025
• 404 DevOps Not Found: The AWS Automation Adventure mk
• When Your DevOps Team Gets Replaced by AI and Then Everything Crashes
• Database Migrations Get the ChatGPT Treatment: Just Vibe Your Schema Changes
• AWS DevOps Team Gets the AI Treatment: 40% Fewer Humans, 100% More Questions
• Breaking Up is Hard to Compute: Microsoft and OpenAI Redefine Their Relationship
• AWS Goes Full Scope: Now Tracking Your Cloud’s Carbon from Cradle to Gate
• Platform Engineering: When Your Golden Path Leads to a Dead End
• DynamoDB’s DNS Disaster: How a Race Condition Raced Through AWS
• AI Takes Over AWS DevOps Jobs, Servers Take Unscheduled Vacation
• PostgreSQL Scaling Gets a 30-Second Makeover While AWS Takes a Coffee Break
• The Domino Effect: When DynamoDB Drops, Everything Drops
• RAG to Riches: Amazon Nova Learns to Cite Its Sources
• AWS Finally Tells You When Your EC2 Instance Can’t Keep Up With Your Storage Ambitions
• AWS Nova Gets Grounded: No More Hallucinating About Reality
• One API to Rule Them All: OneLake’s Storage Compatibility Play
• OpenAI gets to pay Alimony
• Database schema deployments are totally a vibe
• AWS will tell you how not green you are today, now in 3 scopes

02:00 DDoS in September | Fastly

• Fastly‘s September DDoS report reveals a notable 15.5 million requests per second attack that lasted over an hour, demonstrating how modern application-layer attacks can sustain extreme throughput with real HTTP requests rather than simple pings or amplification techniques.
• Attack volume in September dropped to 61% of August levels, with data suggesting a correlation between school schedules and attack frequency: lower volumes coincide with school breaks, while higher volumes occur when schools are in session.
• Media & Entertainment companies faced the highest median attack sizes, followed by Education and High Technology sectors, with 71% of September’s peak attack day attributed to a single enterprise media company.
• The sustained 15 million RPS attack originated from a single cloud-provider ASN, using sophisticated daemons that mimicked browser behavior, making detection more challenging than typical DDoS patterns.
• Organizations should evaluate whether their incident response runbooks can handle hour-long attacks at 15+ million RPS, as these sustained high-throughput attacks require automated mitigation rather than manual intervention.
• Listen, we’re not inviting a DDoS attack, but also…we’ll just turn off the website, so there’s that.

04:41 Google AI Studio updates: More control, less friction

• Google AI Studio introduces “vibe coding” – a new AI-powered develo...