The 10 scariest cloud outages (and lessons learned from them)

5 of 20
  • T-Mobile Sidekick shutdown, 2009

    T-Mobile Sidekick shutdown, 2009

    Think cloud outages can't be terrifying? You haven't been paying attention. Happy Halloween, everybody ...

    In fall 2009, a server failure at Microsoft caused big problems for T-Mobile Sidekick phone owners: They were unable to access their email, calendar info, contacts, and personal data stored in the cloud for a week.

    Photo by: Phil Ramey/RameyPix/Corbis

    Caption by: Fox Van Allen

  • Lessons learned from T-Mobile

    Lessons learned from T-Mobile

    Lessons Learned: If you have important data in the cloud you can't afford to lose, it's worth your time to make a local backup for safekeeping.

    Photo by: CNET

    Caption by: Fox Van Allen

  • Yahoo! Mail outage, 2013

    Yahoo! Mail outage, 2013

    When Yahoo! Mail underwent a major redesign in October 2013, a some users reported that mail items appeared to be missing from their accounts. Ultimately, in December 2013, Yahoo! admitted that there was a failure in 1 percent of its email accounts -- affecting approximately 1,000,000 people -- with some emails going undelivered for weeks or months.

    Photo by: Helen King/Corbis

    Caption by: Fox Van Allen

  • Lessons learned from Yahoo!

    Lessons learned from Yahoo!

    Lessons Learned:A major frustration in this outage was a lack of communication. Yahoo! attempted to minimize the appearance of the disaster when discussing it publicly, while CEO Marissa Mayer was criticized for staying silent.

    When there's an outage companies and executives need to be in front of it.

    Photo by: Ruben Sprich/Reuters/Corbis

    Caption by: Fox Van Allen

  • Hurricane Sandy, 2012

    Hurricane Sandy, 2012

    Hurricane Sandy caused lengthy power outages and extensive flooding in the New York City area, taking a number of servers offline in the region. This caused major websites to fail, including The Huffington Post, BuzzFeed, and Gawker.

    Photo by: Keith Bedford/Reuters/Corbis

    Caption by: Fox Van Allen

  • Lessons learned from Sandy

    Lessons learned from Sandy

    Lessons Learned: Many backup generators failed during Hurricane Sandy because they were submerged in water; others failed when liquid fuel reserves ran out. Having a robust plan for continued operations through natural disasters is critical.

    Photo by: Richard Levine/Demotix/Corbis

    Caption by: Fox Van Allen

  • Amazon Cloud Services outage, 2015

    Amazon Cloud Services outage, 2015

    In September 2015, Amazon Cloud Services servers failed when they were overloaded with metadata requests from a new DynamoDB feature. As a result, many popular apps and websites (Reddit, Tinder, Netflix, IMDB) were offline for seven hours.

    Photo by: Iain Masterton/incamerastock/Corbis

    Caption by: Fox Van Allen

  • Lessons learned from Amazon

    Lessons learned from Amazon

    Lessons Learned: Most Amazon clients were caught unprepared for the outage, but not Netflix. That's because the streaming site uses "chaos engineering" to simulate disruptions, preparing itself for the worst.

    Photo by: Corbis

    Caption by: Fox Van Allen

  • PayPal, 2009

    PayPal, 2009

    In 2009, PayPal experienced a worldwide system outage for approximately five hours. The company handled $2,000 in online commerce every second at the time, suggesting the event interfered with $36 million worth of personal and business transactions.

    Photo by: Yuriko K Nakao/Reuters/Corbis

    Caption by: Fox Van Allen

  • Lessons learned from PayPal

    Lessons learned from PayPal

    Lessons Learned: Mobile payment systems can and do fail. Businesses should support multiple payment systems where possible to give customers options during an outage.

    Photo by: David Shopper/Corbis

    Caption by: Fox Van Allen

  • GoDaddy, 2012

    GoDaddy, 2012

    Initially thought to be the work of an Anonymous-connected hacker, a sizable outage struck web services provider GoDaddy in 2012. The outagee was due to corrupted router table data. Service was down for six hours, putting countless websites and email inboxes out of commission.

    Photo by: ASP/Cal Sport Media/Zumapress.com

    Caption by: Fox Van Allen

  • Lessons learned from GoDaddy

    Lessons learned from GoDaddy

    Lessons Learned: GoDaddy was criticized for having poor infrastructure, poor support and poor communications throughout the crisis. If you have business-critical data in the cloud, it is imperative that you choose your provider wisely.

    Photo by: Hiya Images/Corbis

    Caption by: Fox Van Allen

  • Food Stamps/SNAP, 2013

    Food Stamps/SNAP, 2013

    A power outage at a Xerox Corp. data center wrecked havoc on America's food stamp program in 17 states for more than 11 hours, removing the spending limits from SNAP EBT cards.

    This led to supermarket shelves being "decimated" as shoppers piled their carts full of groceries. Other supermarkets stopped accepting SNAP cards entirely.

    Photo by: Robin Nelson/Zumapress.com

    Caption by: Fox Van Allen

  • Lessons learned from SNAP

    Lessons learned from SNAP

    Lessons Learned: While relatively rare, long cloud outages can happen in crucial areas. It's important to have a game plan in place for dealing with these outages -- many stores simply turned away hungry customers, inciting panic.

    Photo by: Mike Segar/Reuters/Corbis

    Caption by: Fox Van Allen

  • NASDAQ failure, 2013

    NASDAQ failure, 2013

    On Aug. 22, 2013, a software bug in the NASDAQ backup servers caused a total failure, taking the stock exchange offline for more than three hours. When it came back online, traders rushed to sell shares of NASDAQ itself, pushing it 5 percent lower.

    Photo by: Rick Maiman/Sygma/Corbis

    Caption by: Fox Van Allen

  • Lessons learned from NASDAQ

    Lessons learned from NASDAQ

    Lessons Learned: Shortly after the outage, NASDAQ proposed design changes to its Securities Information Processor, "including architectural improvements, information security, disaster recovery plans and capacity parameters."

    Photo by: Steve Prezant/Corbis

    Caption by: Fox Van Allen

  • Intuit Cloud outage, 2010

    Intuit Cloud outage, 2010

    In June 2010, power failures took down both the main and backup servers at financial services company Intuit (Quickbooks, TurboTax). Businesses lost access to their books for 36 hours. Making matters worse, a second failure occurred at Intuit less than a month later.

    Photo by: Mike Blake/Reuters/Corbis

    Caption by: Fox Van Allen

  • Lessons learned from Intuit

    Lessons learned from Intuit

    Lessons Learned: If you need guaranteed, round-the-clock access to your important financial data, keep an offline copy.

    Photo by: Corbis

    Caption by: Fox Van Allen

  • Hotmail database error, 2010

    Hotmail database error, 2010

    At the end of 2010, Microsoft ran a script to delete a number of dummy Hotmail accounts the company had used for testing purposes. An error in the script instead deleted 17,000 legitimate accounts. Account recovery and service restoration took three days in most cases; longer in others.

    Photo by: CNET

    Caption by: Fox Van Allen

  • Lessons learned from Hotmail

    Lessons learned from Hotmail

    Lessons Learned: We all have our preferred email provider. To play it safe, however, it's worth maintaining an account with a second provider to maintain communications in case of emergency.

    Photo by: Imaginechina/Corbis

    Caption by: Fox Van Allen

5 of 20

Hurricane Sandy, 2012

Hurricane Sandy caused lengthy power outages and extensive flooding in the New York City area, taking a number of servers offline in the region. This caused major websites to fail, including The Huffington Post, BuzzFeed, and Gawker.

Caption by: Fox Van Allen

5 of 20

Related Topics:

Digital Transformation Data Centers CXO Innovation Storage Cloud TV

Related Galleries

    • 1 of 3