<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: uptime</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/uptime.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-07-27T17:42:48+00:00</updated><author><name>Simon Willison</name></author><entry><title>Amazon S3 Availability Event: July 20, 2008</title><link href="https://simonwillison.net/2008/Jul/27/aws/#atom-tag" rel="alternate"/><published>2008-07-27T17:42:48+00:00</published><updated>2008-07-27T17:42:48+00:00</updated><id>https://simonwillison.net/2008/Jul/27/aws/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://status.aws.amazon.com/s3-20080720.html"&gt;Amazon S3 Availability Event: July 20, 2008&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Don’t let the newspeak put you off; this is an honest and informative description of the bug that took down S3 last Sunday, although it does include the world’s longest way of saying “we turned it off and on again”.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/amazon"&gt;amazon&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/newspeak"&gt;newspeak&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/s3"&gt;s3&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/uptime"&gt;uptime&lt;/a&gt;&lt;/p&gt;



</summary><category term="amazon"/><category term="newspeak"/><category term="s3"/><category term="uptime"/></entry><entry><title>Amazon S3 Service Level Agreement</title><link href="https://simonwillison.net/2007/Oct/9/sla/#atom-tag" rel="alternate"/><published>2007-10-09T00:52:14+00:00</published><updated>2007-10-09T00:52:14+00:00</updated><id>https://simonwillison.net/2007/Oct/9/sla/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.amazon.com/gp/browse.html?node=379654011"&gt;Amazon S3 Service Level Agreement&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Went in to effect on the 1st of October. Promises 99.9% uptime over a monthly billing cycle or you get “service credits” towards future S3 payments.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://mcmanus.typepad.com/grind/2007/10/amazon-s3-provi.html"&gt;Jeffrey McManus&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/amazon"&gt;amazon&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/aws"&gt;aws&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jeffrey-mcmanus"&gt;jeffrey-mcmanus&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/s3"&gt;s3&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/sla"&gt;sla&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/uptime"&gt;uptime&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/web-services"&gt;web-services&lt;/a&gt;&lt;/p&gt;



</summary><category term="amazon"/><category term="aws"/><category term="jeffrey-mcmanus"/><category term="s3"/><category term="sla"/><category term="uptime"/><category term="web-services"/></entry></feed>