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
Welcome to the new StatusCake blog. You may be confused by thinking we already had a blog so why have we now relaunched it? Previously our blog included all sorts of things including StatusCake updates, industry posts and generally was a mixed mismatched affair. From today all the StatusCake news and updates will be contained within our “News” section of the website and this blog will take on a new role as being a place for our team to write about the technology world around them.
We hope to write at least a post a day about whatever is on our mind; this can be anything from some great resources for creative web designers all the way through to our view on a new startup company.
Our blog will not be filtered through a company filter so to speak and the opinions posted will be that of the poster – this means while you may disagree with some points we hope you understand that it doesn’t reflect a company wide opinion. We also plan to have some guest posts so if you got a message you want to get out there then please do contact us.
It is very much our hope that by creating this blog we will be able to write some genuinely helpful and interesting posts – and hey even give you a few laughs here and there! Please do feel free to get engaged within the comments of the posts and as always we’ll be listening to feedback about this new area of the site.
Finally if you’re worried that we’re going to be spending time on writing the blog posts and not enough of time on the application itself then fear not – posts will be written in the free time that we have. So without further-ado let me once again welcome you to the new StatusCake Blog
James Barnes
Share this
More from StatusCake
Turn StatusCake into a verified alerting and escalation flow with Hermes
6 min read StatusCake tells you that something might be broken. Hermes can check whether it really looks broken, decide who should hear about it, send the email, and keep the record for tomorrow morning’s summary.
Daniel
May 13, 2026
Blog
Beyond Uptime: Building a Self-Healing OpenClaw Observability Stack
3 min read The allure of OpenClaw is undeniable. You deploy a highly autonomous, self-hosted AI agent, give it access to your repositories and inboxes, and watch it reason through complex workflows while you sleep. It is the dream of the ultimate 10x developer tool realized. But as any veteran DevOps engineer will tell you: running an LLM-backed
Daniel
April 23, 2026
When AWS us-east-1 Fails, Much of the Internet Fails With It
7 min read There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure,
James Barnes
April 15, 2026
In the Age of AI, Operational Memory Matters Most During Incidents
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
James Barnes
April 10, 2026
AI Didn’t Kill the SDLC. It Made It Harder to See
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
James Barnes
April 2, 2026
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
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,
James Barnes
March 25, 2026