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
There are lots of different status codes that your web server can return – and to different people, different status codes can mean different things. That’s why from today anyone on a paid plan will be able to define what status codes to alert on – along with the ability to add your own status codes.
This means that if you want to get alerted on a redirect when there shouldn’t be one – you can do so. It also means that you can code your software to return status codes depending on certain internal functions failing such as your database. Finally it means some of the lesser known status codes can now also be supported.
Even if you’re on our free package you benefit from these changes – all the standard status codes are included by default and you can remove any that you don’t want. You can’t however add any custom ones. So to take advantage of custom define status code alerts sign-up for a paid plan today.
If you’re confused about what status codes are and what you do with them – not a problem! You can skip this section in the project set-up and we’ll handle all the standard error status codes without you having to change anything. If you want to read up on what each status code means then Wikipedia has a fantastic article covering each one
StatusCake is constantly growing and improving and this is just the latest of many awesome new additions to our website monitoring service. Stay tuned for even more over the coming weeks and months!
James Barnes
Share this
More from StatusCake
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
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
James Barnes
February 25, 2026
Designing Alerts for Action
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
James Barnes
February 18, 2026
A Notification List Is Not a Team
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
James Barnes
February 11, 2026