[Outages-discussion] S3 Outages Postmortem

[Bob Strecansky]

I was thinking it had to most likely be a networking problem; considering
that it was so abrupt to come off and come on.

On Wed, Mar 1, 2017 at 2:17 PM Kevin Blackham <blackham at gmail.com> wrote:

> I have some insights, but I'm under NDA. This was big enough I expect some
> public disclosure (my words).
>
> I can tell you we observed lots of services affected, not just S3. EBS was
> jacking up IO all over the place, and many machines didn't even ping. SES
> was quite broken, as was autoscaling. One might conclude it was a network
> problem.
>
> On Mar 1, 2017 12:09, "Bob Strecansky" <bob at mailchimp.com> wrote:
>
> Has anyone heard anything about why S3 was down for 5 hours yesterday?
> Usually Amazon doesn't post postmortems, and i'm curious as to what
> happened.
>
> Thanks,
>
> Bob Strecansky
> --
> Thanks,
>
> -B
>
> _______________________________________________
> Outages-discussion mailing list
> Outages-discussion at outages.org
> https://puck.nether.net/mailman/listinfo/outages-discussion
>
> --
Thanks,

-B
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20170301/75aad97e/attachment-0001.html>