<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chaos on Teddy Ferdinand</title><link>https://tferdinand.net/en/tags/chaos/</link><description>Recent content in Chaos on Teddy Ferdinand</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 30 Nov 2020 17:53:04 +0000</lastBuildDate><atom:link href="https://tferdinand.net/en/tags/chaos/index.xml" rel="self" type="application/rss+xml"/><item><title>Turn off the Internet: AWS is no longer responding!</title><link>https://tferdinand.net/en/turn-off-the-internet-aws-is-no-longer-responding/</link><pubDate>Mon, 30 Nov 2020 17:53:04 +0000</pubDate><guid>https://tferdinand.net/en/turn-off-the-internet-aws-is-no-longer-responding/</guid><description>&lt;p&gt;A few days ago, an incident impacting the AWS cloud provider had a significant impact on many companies and services directly affected by this instability.&lt;/p&gt;
&lt;p&gt;I saw on social networks many reactions, often beside the subject (unfortunately) and I thought it could be useful to give you my analysis of the subject.&lt;/p&gt;
&lt;h2 id="rewind"&gt;Rewind&lt;/h2&gt;
&lt;p&gt;Let’s start by recalling the incident a bit.&lt;/p&gt;
&lt;p&gt;On Wednesday evening (French time), AWS encountered a growing number of errors in some of its services in the us-east-1 (North Virginia) region.&lt;/p&gt;</description></item></channel></rss>