44% of outages last year came from an alert someone had already dismissed.
A 2026 survey of over 1,000 SRE, DevOps and IT ops professionals found teams don't miss outages because nothing fired - they miss them because almost everything fires, and the one alert that mattered looked exactly like the noise.
The number behind the noise
A 2026 study of 1,039 site reliability, DevOps and IT ops professionals found that 44% of organizations suffered an outage in the past year directly linked to a suppressed or ignored alert. By the teams' own estimate, 70% of the alerts they receive don't require any action at all. And 83% admitted their team ignores or dismisses alerts at least occasionally - not out of carelessness, but because reading every alert as if it mattered stopped being possible a long time ago.
Why the real alert gets treated like the fake ones
When 7 out of 10 alerts are noise, the brain stops reading them individually and starts pattern-matching: same channel, same tone, same shape as the hundred before it that turned out to be nothing. A separate 2025 study found 75% of UK IT teams had suffered an outage because of a missed alert, and 15% admitted to actively suppressing alerts - above the global average. More tellingly, 78% of teams said they'd had a production failure their monitoring missed entirely. Not because the system stayed quiet. Because by the time it spoke, nobody was still listening.
More monitoring doesn't fix a noise problem
The instinctive response to a missed outage is to add another rule, another dashboard, another threshold. If 70% of the signal is already noise, adding more sensors makes the ratio worse, not better - it trains the team to tune out faster, not slower. Engineers already report losing roughly 40% of their time to firefighting instead of building. The team most overloaded by alerts is also the one most likely to miss the one that counted.
The ACS approach
Before we wire up a new alert, we ask two questions: who acts on this, and what actually happens if it's wrong? An alert with no clear owner or no real consequence is a notification, not a warning, and it belongs in a log, not an inbox someone has learned to mute. We'd rather ship fewer alerts that are each worth opening than a dashboard that's technically watching everything and functionally watched by no one.