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!
Share this
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
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
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
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
Find out everything you need to know in our new uptime monitoring whitepaper 2021