AWS S3 Outage • Hacker News Board

Re: AWS S3 Outage

#71

Post by mentat » Mon, Aug 10, 2015, 9:33 AM UTC

Now updates about ELB scaling and Lambda failures.

Re: AWS S3 Outage

#72

Post by robotfelix » Mon, Aug 10, 2015, 9:35 AM UTC

crodjer wrote: post #21

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

I can't help but be a little surprised that Heroku's entire build system is disabled by an S3 failure in one region. Now I'm unable to add a notice about the issues to my site's HTML...

Re: AWS S3 Outage

#73

Post by eva1984 » Mon, Aug 10, 2015, 9:39 AM UTC

vaibhavrajput wrote: post #70

Why it is behaving like this each other day?

What is the last time that AWS gets two consecutive major outages within, maybe, 30 days?

Re: AWS S3 Outage

#74

Post by kevindeasis » Mon, Aug 10, 2015, 9:39 AM UTC

That would explain why my console was not performing well even if http://status.aws.amazon.com/ says "Service is operating normally", good thing their api seems to be functioning during that outage, for me at least

Re: AWS S3 Outage

#75

Post by addandsubtract » Mon, Aug 10, 2015, 9:40 AM UTC

jbbarth wrote: post #68

kureikain wrote: post #67

It's two hours. Luckily it happenned around 12:00AM otherwise we are having a bad day. Whomever being a DevOps or SysAdmin probably cannot sleep tonight :(. In our case, we put Fastly on top of our assets/images so that only a partil of request get errors. The cached object on Fastly is still fine.

Actually on some parts of the world it's not 12:00AM you know, and there are sysadmins/devops there too :-)

11:40am: Currently can't push to Heroku :(

Re: AWS S3 Outage

#76

Post by ranman » Mon, Aug 10, 2015, 9:40 AM UTC

devastor wrote: post #63

mryan wrote: post #59

Earlier quoted context omitted.

EC2 is not down.

It's up, but launching new instances doesn't work due to the S3 issue.

I can still launch new instances.

Re: AWS S3 Outage

#77

Post by eloisant » Mon, Aug 10, 2015, 9:40 AM UTC

kureikain wrote: post #67

It's two hours. Luckily it happenned around 12:00AM otherwise we are having a bad day. Whomever being a DevOps or SysAdmin probably cannot sleep tonight :(. In our case, we put Fastly on top of our assets/images so that only a partil of request get errors. The cached object on Fastly is still fine.

Our European customers are not amused.

Re: AWS S3 Outage

#78

Post by hughstephens » Mon, Aug 10, 2015, 9:41 AM UTC

Next update is live

  2:38 AM PDT We continue to execute on our recovery plan
  and have taken multiple steps to reduce latencies and error
  rates for Amazon S3 in US-STANDARD. Customers may continue 
  to experience elevated latencies and error rates as we 
  proceed through our recovery plan.

Re: AWS S3 Outage

#79

Post by crodjer » Mon, Aug 10, 2015, 9:43 AM UTC

robotfelix wrote: post #72

crodjer wrote: post #21

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

I can't help but be a little surprised that Heroku's entire build system is disabled by an S3 failure in one region. Now I'm unable to add a notice about the issues to my site's HTML...

True. Given the business Heroku is in, they should have redundancies in multiple regions if not multiple service providers.

Re: AWS S3 Outage

#80

Post by [deleted] » Mon, Aug 10, 2015, 9:43 AM UTC

vaibhavrajput wrote: post #70

Why it is behaving like this each other day?

[deleted]