Amazon Cloud Outrage

[kladner]

As of 20:37 UTC this seems to be ongoing.

SAN FRANCISCO — Portions of Amazon Web Services, the nation's largest cloud computing company, went offline Tuesday afternoon, affecting millions of companies across the United States .


"This is a pretty big outage," said Dave Bartoletti, a cloud analyst with Forrester. "AWS had not had a lot of outages and when they happen, they're famous. People still talk about the one in September of 2015 that lasted five hours," he said.

“As our business is in bamboo plants, pictures are a very important part of selling our product online. We use Amazon S3 to store and distribute our website images. When Amazon’s servers went down, so did the majority of our website,” said the company's chief technology officer Daniel Mullaly.

I thought of Paul with the underlined.

Here is Amazon's own tracking. https://status.aws.amazon.com/?tag=b0c55-20

[kladner]

It still seems problematic. The status page still has lots of red and yellow icons, and "Increased Error Rate" tags.
Increased Error Rates

Update at 1:12 PM PST: S3 object retrieval, listing and deletion are fully recovered now. We are still working to recover normal operations for adding new objects to S3.
Update at 12:52 PM PST: We are seeing recovery for S3 object retrievals, listing and deletions. We continue to work on recovery for adding new objects to S3 and expect to start seeing improved error rates within the hour.
Update at 11:35 AM PST: We have now repaired the ability to update the service health dashboard. The service updates are below. We continue to experience high error rates with S3 in US-EAST-1, which is impacting various AWS services. We are working hard at repairing S3, believe we understand root cause, and are working on implementing what we believe will remediate the issue.

[retina]

Putting all your trust into one company is a good idea. What could possibly go wrong?

[kladner]

They say their issues are resolved.

[RESOLVED] Increased Error Rates for Amazon S3

Update at 2:08 PM PST: As of 1:49 PM PST, we are fully recovered for operations for adding new objects in S3, which was our last operation showing a high error rate. The Amazon S3 service is operating normally.
Update at 1:12 PM PST: S3 object retrieval, listing and deletion are fully recovered now. We are still working to recover normal operations for adding new objects to S3.
Update at 12:52 PM PST: We are seeing recovery for S3 object retrievals, listing and deletions. We continue to work on recovery for adding new objects to S3 and expect to start seeing improved error rates within the hour.
Update at 11:35 AM PST: We have now repaired the ability to update the service health dashboard. The service updates are below. We continue to experience high error rates with S3 in US-EAST-1, which is impacting various AWS services. We are working hard at repairing S3, believe we understand root cause, and are working on implementing what we believe will remediate the issue.

[ewmayer]

Have any MSM outlets blamed The Putin for the outage yet?

[chalsall]

Originally Posted by ewmayer

Have any MSM outlets blamed The Putin for the outage yet?

I would be surprised if they were that stupid.

[kladner]

Originally Posted by ewmayer

Have any MSM outlets blamed The Putin for the outage yet?

Give 'em time.

[Dr Sardonicus]

Originally Posted by ewmayer

Have any MSM outlets blamed The Putin for the outage yet?

As of March 2, there seems to be very little media coverage, beyond initial reports that the outage occurred.

Checking the AMAZON cloud status board on March 1 showed mostly green, except in northern Virginia. That could be cloud-related in another sense -- severe weather in the area at the time.

As far as speculation about the big outage being caused by nefarious doings, I did manage to dredge up a comment at Zerohedge as follows:

Cyber attack by White House on Bezos? What if this is payback to WaPo?