Official cause of the S3 issue was... a typo. …

Post by

Kristine Stewart

2017-03-02Edited

Official cause of the S3 issue was... a typo.

http://www.theverge.com/2017/3/2/14792442/amazon-s3-outage-cause-typo-internet-server

How a typo took down S3, the backbone of the internetEarlier this week, much of the internet ground to a halt when the servers that power them suddenly vanished. The servers were part of S3, Amazon’s popular web hosting service, and when they went...

3 Comments

LVL 7

Comment

by:Brian Matis

2017-03-02

That's quite a tpyo!

LVL 21

Comment

by:Lucas Bishop

2017-03-02

Seems kind of unfair to blame one person's typing in a terminal. Sounds more like a lack of safe-measures by Amazon.

LVL 19

Comment

by:Phil Phillips

2017-03-03

Amazon definitely realized the lack of safe-measures - they've updated their systems to remove capacity much more slowly, and also added a minimum required capacity level. I guess they realized that a minimum required capacity level of 0 isn't good ;).

Recommended Posts

LVL 55

Post by

M A

4d ago

Exchange Server Roadmap Update.
MS have moved the release date for the next version of Exchange Server to the second half of 2025.
It requires Server and CAL licenses and will be accessible only to customers with Software Assurance,
https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-roadmap-update/ba-p/3421389