Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



This week the StatusCake team are going to be at the following events. Get in touch by email us or live chat on the StatusCake website if you’d like to meet us.
Our dev ops team will be at the Influx Roadshow in Amsterdam this Wednesday. The team are looking forward to meeting other developers who use InfluxDB, the time series database platform. The focus will be looking at how other Influx customers use the database, taking a look at InfluxDB’s new cloud offering, as well as their product roadmap.
Our CEO James Barnes will be at Big Data LDN talking with and learning from leading data and analytics experts and teams about what “big data” really means in practice, what an effective customer focused data-driven strategy might look like, and how to deliver that vision.
James will also be at Twilio’s Engage conference with Mario Giraldo, head of StatusCake Partners on Thursday afternoon where the focus is not only on looking at the way in which we engage and communicate with our own customers through using products and technologies similar to Twilio’s, but also how we can build out our own innovative customer engagement strategies and experiences using APIs.
Our head of tech Hemm Kerrai will be at the New Age of DevOps events by Women in DevOps and hosted by Conde Nast.
The event will feature a panel includes: Fudma Mohammed, software engineer at Conde Nast; Susie Colman, senior software engineer at BBC; Gabrielle Anderson, senior site reliability engineer at Google; and Anna Szyoyi, engineering manager at Improbable.
Hemm Kerrai will be attending the GDG DevFest event in London this coming Saturday. Hosted by Google, and King College London Tech Society the Devfest is a multrack event looking at everything from emerging technologies, mobile, and cloud and machine learning.
If you’d like to meet the team and arrange a meeting at any of these events please email us.
Share this
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
Find out everything you need to know in our new uptime monitoring whitepaper 2021