Editing Amazon web services outages

== Amazon Web Services outages ==
{| class="wikitable sortable"
|-
! Year !! Month and date (if available) !! Event type !! Details
|-
| 2011 || April 21 || Outage partial availability zone || At 12:47 AM PDT on April 21, an invalid traffic shift prior to network upgrade caused EBS instances to lose connectivity to one another with an availability zone of US-East-1 region. Once the errors were localized to just one availability zone, the EBS recovery These connectivity errors impacted EBS volume and EC2 instances in multiple availability zones and caused issues for customers until full recovery at 3:00 PM PDT on April 24.<ref>{{cite web |url = https://aws.amazon.com/message/65648/ |title=Summary of the Amazon EC2 and Amazon RDS Service Disruption in the US East Region |website = aws.amazon.com |date=2011-04-29 |access-date=2018-11-13}}</ref><ref>{{cite web |url = https://www.crn.com/news/cloud/229402004/amazon-ec2-goes-dark-in-morning-cloud-outage.htm |title = Amazon EC2 Goes Dark In Morning Cloud Outage |publisher=CRN |date=2011-04-21 |access-date=2018-11-13 }}</ref>
|-
| 2011 || August 7 || Outage || Power lost in Ireland, EU West region, causing disruption and outage "service disruption began at 10:41 AM PDT on August 7th"<ref>{{cite web |url = https://aws.amazon.com/message/2329B7/ |title=Summary of the Amazon EC2, Amazon EBS, and Amazon RDS Service Event in the EU West Region |publisher=AWS |date=2011-08-16 |access-date=2021-03-19 }}</ref> (also mentioned but distinct from the outtage mentioned above; it happened around the same time as the US outtage). Due to followup issues, full restoration of e g EBS and RDS took in the order of days.<ref>{{cite web |url = https://sociable.co/business/amazon-admits-lightening-didnt-strike-its-dublin-data-center-but-a-series-of-errors-did/ |title=Amazon admits lightning didn't strike its Dublin Data center, but a series of errors did |publisher=The Sociable |date=2011-08-16 |access-date=2021-03-19 }}</ref>
|-
| 2011 || August 8 || Outage || EC2 went down around 10:25&nbsp;p.m. Eastern in Amazon's U.S. East Region. The cloud outage lasted roughly 30 minutes, but took down the Web sites and services of many major Amazon cloud customers, including Netflix, Reddit and Foursquare. The issue happened in the networks that connect the Availability Zones to the Internet and was primarily caused by a software bug in the router.<ref>{{cite web |url = https://www.crn.com/news/cloud/231500023/amazon-offers-explanations-apologies-for-dual-cloud-outages.htm |title=Amazon Offers Explanations, Apologies For Dual Cloud Outages |publisher=CRN |date=2011-08-16 |access-date=2018-11-13 }}</ref>
|-
| 2012 || June 29 || Service disruption availability zone || A major disruption occurs to the EC2, EBS, and RDS services in a single availability zone (due to a large scale electrical storm which swept through the Northern Virginia area).<ref>{{cite web |url = https://aws.amazon.com/message/67457/ |title = Summary of the AWS Service Event in the US East Region |website = Aws.amazon.com |date=2012-07-02 |access-date=2018-08-29 }}</ref>
|-
| 2012 || October 22 || Outage || A major outage occurs (due to latent memory leak bug in an operational data collection agent), affecting many sites such as [[Reddit]], [[Foursquare City Guide|Foursquare]], [[Pinterest]], and others.<ref>{{cite web |url=https://aws.amazon.com/message/680342/ |title=Summary of the October 22, 2012 AWS Service Event in the US-East Region |website=aws.amazon.com |date=2012-10-22 |access-date=2013-07-17 }}</ref>
|-
| 2012 || December 24 || Outage || AWS suffers an outage, causing websites such as [[Netflix]] instant video to be unavailable for customers in the Northeastern United States.<ref>{{cite web |url = https://aws.amazon.com/message/680587/ |title=Summary of the December 24, 2012 Amazon ELB Service Event in the US-East Region |website = aws.amazon.com |date=2012-12-24 |access-date=2018-08-30 }}</ref><ref>{{cite web |last=Bishop |first=Bryan |title=Netflix streaming down on some devices due to Amazon issues |url = https://www.theverge.com/2012/12/24/3801978/netflix-streaming-down-on-some-devices-thanks-to-amazon-issues |website=The Verge |date=24 December 2012 |access-date=5 February 2013 }}</ref>
|-
| 2013 || September 13 || Outage || AWS US-East-1 region experienced network connectivity issues affecting instances in a single Availability Zone. We also experienced increased error rates and latencies for the EBS APIs and increased error rates for EBS-backed instance launches.<ref>{{cite web |url = https://gigaom.com/2013/09/13/uh-oh-amazon-u-s-east-is-in-trouble-again/ |title=Uh oh. Amazon U.S. East is in trouble again |publisher=Gigaom |date=2013-09-13 |access-date=2018-11-13 }}</ref>
|-
| 2014 || November 26 || Service disruption || [[Amazon CloudFront]] DNS server went down for two hours, starting at 7:15&nbsp;p.m. EST. The DNS server was back up just after 9 p.m. Some websites and cloud services were knocked offline as the content delivery network failed to fulfill DNS requests during the outage. Nothing major, but worthy of this list because it involved the world's biggest and longest-running cloud.<ref>{{cite web |url = https://www.theregister.co.uk/2014/11/27/aws_cloudfront_wobbles_at_worst_possible_time/ |title = AWS CloudFront wobbles at worst possible time |website = [[The Register]] |date = November 27, 2014 |access-date = November 12, 2018 }}</ref>
|-
| 2015 || September 20 || Outage || The [[Amazon DynamoDB]] service experiences an outage in an availability zone in the us-east-1 (North Virginia) region, due to a power outage and inadequate failover procedures. The outage, which occurs on a Sunday morning, lasts for about five hours (with some residual impact till Monday) and affects a number of related Amazon services include [[Simple Queue Service]], EC2 autoscaling, [[Amazon CloudWatch]], and the online AWS console.<ref>{{cite web |url = https://aws.amazon.com/message/5467D2/ |title = Summary of the Amazon DynamoDB Service Disruption and Related Impacts in the US-East Region |publisher = [[Amazon Web Services]]|date = September 21, 2015 |access-date = December 5, 2016 }}</ref> A number of customers are negatively affected, including [[Netflix]], but Netflix is able to recover quickly because of its strong disaster recovery procedures.<ref>{{cite magazine |url = http://www.techrepublic.com/article/aws-outage-how-netflix-weathered-the-storm-by-preparing-for-the-worst/ |title = AWS outage: How Netflix weathered the storm by preparing for the worst. Despite being run entirely from AWS' cloud platform the online streaming giant Netflix reports a quick recovery from Sunday's disruption - demonstrating the importance of its approach of building cloud-based systems to "fail". |last = Heath|first = Nick|date = September 21, 2015 |access-date = December 5, 2016 |magazine = TechRepublic }}</ref>
|-
| 2016 || June 5 || Outage || AWS Sydney experiences an outage for several hours as a result of severe thunderstorms in the region causing a power outage to the data centers.<ref>{{cite web |url = https://aws.amazon.com/message/4372T8/ |title=Summary of the AWS Service Event in the Sydney Region |website = aws.amazon.com |date=2016-06-05 |access-date=2018-08-29}}</ref><ref>{{cite web |url = https://www.theregister.co.uk/2016/06/05/aws_oz_downed_by_weather/ |title = AWS endures extended outage in Australia. Heavy clouds take out clouds |last = Chirgwin |first = Richard|date = June 5, 2016 |access-date = December 5, 2016 |website = [[The Register]] }}</ref><ref>{{cite web |url = http://www.itnews.com.au/news/failure-in-power-redundancy-triggered-aws-sydney-outage-420656|title = Failure in power redundancy triggered AWS Sydney outage. Failure in power redundancy triggered AWS Sydney outage |last = Coyne |first = Allie |date = June 9, 2016 |access-date = December 4, 2016 }}</ref>
|-
| 2017 || February 28 || Outage || Amazon experiences an outage of S3 in us-east-1.<ref>{{cite web|url=https://aws.amazon.com/message/41926/ |title=Summary of the Amazon S3 Service Disruption in the Northern Virginia (US-EAST-1) Region |date=2017-02-28 |access-date=2018-08-30}}</ref> There are also related outages for other services in us-east-1 including CloudFormation, autoscaling, Elastic MapReduce, Simple Email Service, and Simple Workflow Service. A number of websites and services using S3, such as [[Medium (website)|Medium]], [[Slack (software)|Slack]], [[Imgur]] and [[Trello]], are affected. AWS's own status dashboard initially fails to reflect the change properly due to a dependency on S3.<ref>{{cite news |url = https://techcrunch.com/2017/02/28/amazon-aws-s3-outage-is-breaking-things-for-a-lot-of-websites-and-apps/|title = Amazon AWS S3 outage is breaking things for a lot of websites and apps |last = Etherington|first = Darrell|date = February 28, 2017|access-date = February 28, 2017|work = [[TechCrunch]]}}</ref><ref>{{cite news |url = https://www.usatoday.com/story/tech/news/2017/02/28/amazons-cloud-service-goes-down-sites-scramble/98530914/|title = Amazon's cloud service has outage, disrupting sites|newspaper = [[USA Today]]|date = February 28, 2017|access-date = February 28, 2017}}</ref><ref>{{cite web |url = http://www.zdnet.com/article/aws-s3-problem-at-major-data-center-location-brings-down-websites/|title = AWS investigating S3 problem at major data center location. AWS is investigating a problem with S3 storage in its US-East region, its oldest data center, which has impacted several businesses. |last = Condon |first = Stephanie |website = [[ZDNet]] |date = February 28, 2017 |access-date = February 28, 2017 }}</ref> On March 2, AWS reveals that the outage was caused by an incorrect parameter passed in by an authorized employee while running an established playbook, that ended up deleting more instances than the employee intended.<ref>{{cite news |url = https://venturebeat.com/2017/03/02/aws-apologizes-for-february-28-outage-takes-steps-to-prevent-similar-events/ |title = AWS apologizes for February 28 outage, takes steps to prevent similar events |last = Novet |first = JOrdan |date = March 2, 2017 |access-date = March 2, 2017 |work = [[VentureBeat]]}}</ref>
|-
| 2018 || March 2 || Service degradation || Starting 6:25 AM PST, Direct Connect experienced connectivity issues related to a power outage issue in their US-East-1 Region. This caused customers to have service interruptions in reaching their EC2 instances. Issue was resolved fully by 10:26 AM PST.<ref>{{cite web |url = https://virtualizationreview.com/articles/2018/03/05/aws-outage.aspx |title=Hundreds of Enterprise Services Reportedly Hit by AWS Outage |website=The Register |date=2018-03-05 |access-date=2019-02-01}}</ref>
|-
| 2018 || May 31 || Outage || Beginning at 2:52 PM PDT a small percentage of EC2 servers lost power in a single Availability Zone in the US-EAST-1 Region. This resulted in some impaired EC2 instances and degraded performance for some EBS volumes in the affected Availability Zone. Power was restored at 3:22 PM PDT.<ref>{{cite web |url = https://www.theregister.co.uk/2018/06/01/aws_outage/ |title = AWS outage killed some cloudy servers, recovery time is uncertain |website=The Register |date=2018-06-01 |access-date=2018-11-13 }}</ref>
|-
| 2019 || August 23 || Outage || A number of EC2 servers in the Tokyo region shut down due to overheating at 12:36pm local time, due to a failure in the datacenter control and cooling system.<ref>{{cite web |url=https://aws.amazon.com/message/56489/ |title=Summary of the Amazon EC2 and Amazon EBS Service Event in the Tokyo (AP-NORTHEAST-1) Region |website=AWS |access-date=2020-12-02}}</ref>
|- 
| 2019 || August 31 || Outage and data loss || The US-EAST-1 data center suffered a power failure at 4:33am local time, and the backup generators failed at 6am. According to AWS, this affected 7.5 percent of the EC2 instances in one of the ten data centers in one of the six Availability Zones in US-EAST-1. However, after restoring power, a number of EBS volumes, which store the filesystems of the EC2 cloud servers, were permanently unrecoverable. This caused downtime for companies such as Reddit.<ref>{{cite web |url=https://www.whizlabs.com/blog/amazon-aws-outage/ |date=2019-09-23 |access-date=2020-12-02 |website=WhizLabs |title=Amazon AWS Outage}}</ref><ref>{{cite web |url=https://www.bleepingcomputer.com/news/technology/amazon-aws-outage-shows-data-in-the-cloud-is-not-always-safe/ |date=2019-09-05 |access-date=2020-12-02 |title=Amazon AWS Outage Shows Data in the Cloud is Not Always Safe |website=BleepingComputer}}</ref><ref>{{cite web |url=https://www.cloudsavvyit.com/5590/ebs-volumes-arent-safe-from-failure-backup-to-s3/ |title=AWS EBS Volumes Aren't Safe from Failure, Backup to S3 |date=2020-07-27 |access-date=2020-12-02 |website=CloudSavvyIT}}</ref>
|- 
| 2019 || October 22-23 || Service degradation from DDoS || AWS sustained a distributed denial of service attack which caused intermittent DNS resolution errors (for their Route 53 DNS service) from 10:30am PST to 6:30pm PST.<ref>{{cite web |url=https://www.crn.com.au/news/aws-hit-by-ddos-attack-dragging-half-of-web-down-532842 |title=AWS hit by DDoS attack dragging half of web down |date=2019-10-23 |access-date=2020-12-02 |website=CRN}}</ref>
|-
| 2020 || November 25 || Outage || Beginning at 9:52 AM PST the [[Kinesis Data Streams]] API became impaired in the US-EAST-1 Region. This prevented customers from reading or writing data.<ref>{{cite web |url=https://www.theverge.com/2020/11/25/21719396/amazon-web-services-aws-outage-down-internet |title=Prolonged AWS outage has taken down a big chunk of the internet, recovery may take 'a few hours' |website=The Verge|date=25 November 2020 |access-date=26 November 2020 }}</ref>
|}

== See also ==
* {{AWS SLA}}
* {{AWS}}

{{CC}}. Source: wikipedia