Earlier quoted context omitted.
Mapbox and Hipchat too https://www.mapbox.com/status/ https://status.hipchat.com/
Feels like internet is not anymore distributed thing that if one website/node goes down others keep working... Feels like in future... If cloud provider goes down... All internet will stop working :)
AWS S3 Outage
61–70 of 142 posts
Re: AWS S3 Outage
#62Latest Update from http://status.aws.amazon.com/ : 1:52 AM PDT We are actively working on the recovery process, focusing on multiple steps in parallel. While we are in recovery, customers will continue to see elevated error rate and latencies.
Re: AWS S3 Outage
#63even ec2 is down: Amazon Elastic Compute Cloud (N. Virginia) Increased API Error Rates 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.
EC2 is not down.
Re: AWS S3 Outage
#64Latest Update from http://status.aws.amazon.com/ : 1:52 AM PDT We are actively working on the recovery process, focusing on multiple steps in parallel. While we are in recovery, customers will continue to see elevated error rate and latencies.
The icon got yellow. I repeat: YELLOW
Re: AWS S3 Outage
#65Latest Update from http://status.aws.amazon.com/ : 1:52 AM PDT We are actively working on the recovery process, focusing on multiple steps in parallel. While we are in recovery, customers will continue to see elevated error rate and latencies.
Re: AWS S3 Outage
#66Latest Update from http://status.aws.amazon.com/ : 1:52 AM PDT We are actively working on the recovery process, focusing on multiple steps in parallel. While we are in recovery, customers will continue to see elevated error rate and latencies.
The icon got yellow. I repeat: YELLOW
Re: AWS S3 Outage
#67Whomever 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.
Re: AWS S3 Outage
#68It'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.
Re: AWS S3 Outage
#69It'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.