AWS S3 Outage • Hacker News Board

Re: AWS S3 Outage

#21

Post by crodjer » Mon, Aug 10, 2015, 7:59 AM UTC

Could this be a reason why Heroku is misbehaving? https://status.heroku.com/incidents/792K

Re: AWS S3 Outage

#22

Post by cperciva » Mon, Aug 10, 2015, 8:00 AM UTC

gschier wrote: post #19

fizx wrote: post #16

I wonder what it would take for amazon to show one of the yellow icons on their status page? Has it ever happened? Would a datacenter have to fall in the ocean?

Ya, it bothers me that their status messages for major outages are simply "elevated error rates".

I'm sure "elevated error rates" is the first alarm which goes off. And once they've put that description onto the status page, they're probably more worried about getting it fixed than going back and changing the wording.

Re: AWS S3 Outage

#23

Post by jschorr » Mon, Aug 10, 2015, 8:01 AM UTC

kernel_sanders wrote: post #18

Can't launch instances in EC2 in US-East-1 at the moment.

It appears EC2 is affected as well now:

12:51 AM PDT We are investigating increased error rates for the EC2 APIs and launch failures for new EC2 instances in the US-EAST-1 Region.

Re: AWS S3 Outage

#24

Post by [deleted] » Mon, Aug 10, 2015, 8:03 AM UTC

[deleted]

Re: AWS S3 Outage

#25

Post by mrsirduke » Mon, Aug 10, 2015, 8:05 AM UTC

cperciva wrote: post #22

gschier wrote: post #19

Earlier quoted context omitted.

Ya, it bothers me that their status messages for major outages are simply "elevated error rates".

I'm sure "elevated error rates" is the first alarm which goes off. And once they've put that description onto the status page, they're probably more worried about getting it fixed than going back and changing the wording.

They should worry about that a lot. Amazon are notoriously bad at communicating during outages. They've gotten better, but they're big enough that it should have priority.

Re: AWS S3 Outage

#26

Post by cperciva » Mon, Aug 10, 2015, 8:09 AM UTC

mrsirduke wrote: post #25

cperciva wrote: post #22

Earlier quoted context omitted.

I'm sure "elevated error rates" is the first alarm which goes off. And once they've put that description onto the status page, they're probably more worried about getting it fixed than going back and changing the wording.

They should worry about that a lot. Amazon are notoriously bad at communicating during outages. They've gotten better, but they're big enough that it should have priority.

I agree. I was speculating, not trying to defend. :-)

Re: AWS S3 Outage

#27

Post by blowski » Mon, Aug 10, 2015, 8:09 AM UTC

I'm also having issues connecting to buckets based in Ireland (eu-west-1). Just hangs at authentication stage. Tried from 3 different internet connections, all having the same problem.

Re: AWS S3 Outage

#28

Post by JoshGlazebrook » Mon, Aug 10, 2015, 8:10 AM UTC

I'm assuming this is also why I can't start any instances.

> 12:51 AM PDT We are investigating increased error rates for the EC2 APIs and launch failures for new EC2 instances in the US-EAST-1 Region.

Re: AWS S3 Outage

#29

Post by rpmartz » Mon, Aug 10, 2015, 8:13 AM UTC

JoshGlazebrook wrote: post #28

I'm assuming this is also why I can't start any instances. > 12:51 AM PDT We are investigating increased error rates for the EC2 APIs and launch failures for new EC2 instances in the US-EAST-1 Region.

Same here

Re: AWS S3 Outage

#30

Post by dutchbrit » Mon, Aug 10, 2015, 8:13 AM UTC

simonpantzare wrote: post #12

Seeing the same thing. Got back from vacation an hour ago, probably related. :)

Welcome back!