![]() Cloud-based applications, including Microsoft 365, Dynamics and Azure DevOps, were also impacted. ![]() Was the outage due to a misconfiguration? In any case, redundant systems did not kick in.Ī nearly three-hour global outage affecting core Microsoft cloud services, including compute, storage, an application development platform, Active Directory and SQL database services. The outage was referred to as a “technical issue.” Although recovery was fairly quick, damage was significant. Affected airlines included Southwest, SkyWest, United, Delta, United Continental, JetBlue and Alaskan Airlines. (In 2015, CenturyLink was fined $16m for a six-hour 911 outage.)įacebook’s first, but not only, outage of 2019, lasted 14 hours and was reportedly the result of a “ server configuration change.” Things happen, but why didn’t redundant systems take over? See our post on the FB outage.ĪeroData (weight and balance calculations for flight planning)Ī “mere” 40 minute outage delayed close to 3,000 flights. The outage was attributed to equipment failure exacerbated by a network configuration error redundant systems did not take over. Additionally, customers could not make ATM withdrawals, access sensitive patient healthcare records, and more. These subscribers and others in the UK and Singapore lost connectivity for two days. No.ĬenturyLink (communication, network and related services)Ģ2 million subscribers in 39 states were affected by an outage and 17 million customers across 29 US states were unable to reach emergency 911 services and at least 886 calls to 911 were not delivered. Many outages occur when the transition to the secondary site fails to take place. As a rule, when a system becomes unavailable, a secondary, redundant, site should take over operations. Not every enterprise will let the public know why its site went down and will often issue a non-informative reason, attributing the outage to a software or computer “glitch.” Usually, “glitch” can be interpreted as a misconfiguration or a failure of redundant systems to failover (see our post on this). IT outages due to technical software or hardware issuesĪs our table below shows, software or hardware issues are the key reasons organizations experience outages/unavailability and performance disruptions. Generally, the outages fall into three categories: technical software or hardware issues unusually high traffic / load cyberattacks and/or ransomware. To help you place the outages in the right context of reasons why whole environments went down, we’ll review the causes leading to the outages covered here. In other words, no one, not even cloud providers themselves, is immune against outages! ![]() Outages seem to escape any clear classification they span industry segments (we’ve seen dramatic outages in financial services, social media, airlines, telco, retail, etc.), they cover both new and well established infrastructures (from pure public-cloud infrastructure, to “traditional” IT, and any hybrid permutation in between), and impact enterprises of all sizes. We’ll admit, though, that a couple made it onto the list because they were unusual, sort of groundbreakers. number of people/systems affected and, 3. ![]() What makes an outage bad enough to warrant a place on our list? We decided on three criteria to use for listing an outage: 1. So, without too much further ado, we present to you our list of 19 of the worst IT outages of 2019. One, while most lists are described as the “best of,” ours can be described as the “worst of.” Two, our list doesn’t have 10 items, but 19, in line with the number of years into the 21 st century. You know how at the end of every year lists are created intending to reflect, usually, 10 of the year’s best examples of a particular phenomenon or event? Well, we’ve also compiled a list but ours has a couple of twists.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |