Sunday, November 22, 2026
English edition

Development

How to tell a cyberattack from a plain old outage

November 19, 2026 Development Source: Ars Technica

How to tell a cyberattack from a plain old outage

Share this article

So in the interest of soothing the country’s rattled nerves and helping us all find ground truth amid seemingly endless tech catastrophes, we at WIRED present our general guide to determining whether a tech outage is the result of a cyberattack. So take a breath—maybe open the bunker door to let in some fresh air—and read on. The process of determining the cause of an IT service outage should begin with the assumption that it was an accident, says cybersecurity researcher Doug Madory. As the head of Internet analysis at the network security firm Infoblox, Madory says he monitors as many as a dozen network outages a day. Only around “one in a thousand,” he says, turns out to have been caused by hackers. “One’s default position should be that it isn’t a cyberattack,” he says, “unless there is some concrete evidence to the contrary.” Given the rarity of cyberattacks compared to outages as a whole, it’s wise to look at other potential causes first. “Most big outages that look like attacks are self-inflicted,” says João Tomé, the Internet research editor at network data company IPinfo. (In response to WIRED’s questions, Tomé also wrote his own guide for distinguishing outages from cyberattacks.) The usual suspects, he says, include “a bad update, a configuration change, a cable cut, or a power failure.” In the scramble to understand what’s really happening with a given outage, it can sometimes be difficult to tell which sites and services are actually down. And there can be a few reasons for this muddled picture. Sometimes, an outage occurs within a foundational service like a big cloud provider. Major downtime within Amazon Web Services, for example, can cause a cascade of other failures among the company’s customers, who are all dependent on that infrastructure. In other cases, multiple services can seem to be having outages and producing errors but are functioning normally and only having problems when they interact with an entity that’s down. This appears to have been the case in this week’s bank outage: Multiple banks appeared to be having issues, but they all seem to have been linked to certain inter-institutional transactions that involved JPMorgan Chase. Another good example of this scenario is situations where it may appear that multiple wireless carriers are struggling, but all of the failed calls actually involve one network that’s having an outage. On top of these, there are also scenarios where one or more large services are down, and false (typically accidental or anecdotal) reports of additional outages create further confusion and opacity. It can all feel overwhelming, even impossible, to attempt to parse these situations yourself—but there is a concrete place to start. If you think a website or service from a major tech company may be down, look for acknowledgment of the situation on their verified social media accounts or in the “newsroom” press release section of their websites. And keep in mind that you can find these pages and social media accounts through search engines, so you definitely don’t need to be familiar with every company’s communications strategy. Use this same approach for government agencies and other institutions. Another concrete and vital source of information that you can find through search engines is what’s often known as “status dashboard” pages. Large digital platforms specifically offer these informational pages to provide transparency into whether different components of their service are functioning normally or dealing with issues. In a major incident, companies often thread incremental updates about system restoration on the status dashboard. AWS, Google Cloud Platform, and Microsoft Azure all offer these landing pages, and there are similar ones for other services like Meta business products, Google Workspace, telecom companies, AI companies, and so on. Ransomware gangs, perhaps the most common source of serious malicious Internet disruption, publicize their breaches on dark web pages that list their targets for the purposes of extortion, sometimes with a countdown timer designed to pressure victims to pay before they leak stolen information. In other cases, like the NotPetya or WannaCry worms—two of the worst cyberattacks in history—the hackers’ self-perpetuating code left behind ransom messages on machines that quickly spread on social media as the attacks unfolded. Ideological “hacktivist” groups—or state-sponsored hackers working for military or intelligence agencies but posing as hacktivists—also often take credit for their cyberattacks on platforms like X, Telegram, or their own websites. These messages then quickly spread to social media and through news reports. Even these statements, however, should be taken as just another significant data point: Hacker groups exaggerate, misdirect, or lie when it serves their purposes. And some significant mass hacking incidents—such as the Mirai attack on the Internet infrastructure company Dyn in 2016 that took down thousands of websites—have been accompanied by no public message at all from the hackers responsible. In cases where neither the perpetrator of a hacking incident nor its target has confirmed the attack, confirmation can sometimes come first from a government agency—such as the Cybersecurity and Infrastructure Security Agency—or even from threat intelligence researchers at private cybersecurity firms. Government and industry investigators sometimes post their findings to their websites or share them with media, but it often takes days, weeks, or even months to come to confirmed conclusions. Hence, step five. If all these other measures of determining the cause of an outage don’t offer a clear understanding of the situation, the best approach may be patience. “It’s going to get a little conclusive at some point,” Madory says. “Sometimes you just have to just sit and wait.” Aside from the time it takes for companies to admit to their screwups—or hackers to claim a win—the length of an outage can also sometimes offer a clue to its cause. A faulty update, power outage, or cascading bug can often be resolved quickly. Determined hackers who have maximized their damage, who shift tactics to outsmart defenders, or who may still be in a network they’ve breached can cause far longer and more severe outages. “A rollback takes minutes or hours,” Tomé says, referring to reverting to older code as a fix for a faulty update that introduces a bug. “Ransomware takes days or sometimes even weeks.” In other words, as with all breaking news, when facts are in short supply, it’s better to maintain skepticism about early rumors or conspiracy theories and wait for more concrete evidence. In the information vacuum that precedes that evidence, it can be easy to see connections between events that may just be coincidences. What are the odds, you may ask, that five major IT outages occurred on a sequential Thursday, Friday, Monday, and Tuesday? For Doug Madory, who tracks those network outages every day of the week, that string of failures may just be a sign of the increasing complexity of technology—and how fundamentally our civilization has come to depend on it. “For better or worse, modern society is completely mediated through Internet-based services. They have outages from time to time. And that’s a reality I don’t think we’ll ever completely eliminate,” Madory says. “If you’re immersed in that world of looking at outages for years on end, then they don’t really surprise you,” he adds. “You just try to understand what’s different about each one. And maybe what we can learn from it.” This story originally appeared on wired.com.