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
We’ve got a few things to bring you up to speed with today, and you can find all the information below!
New Alert log feature
Our new Alert Log feature gives you a high level of visibility on alerts that have been sent out by our system, you can see the timing, and status of any alert we send no matter the alerting method.
This new feature is available for all plans, so you can take advantage of the data whether you are on our free or Enterprise package! You’ll be given the reasons for any alert failures, some examples including running out of SMS credits and incorrect contact details. As well as a full log of all alerts sent out, with this tool you can also see logs of reports generated by features like Virus Scan.
You can access this new feature by going to the Contact Groups section of your account, and from here you can see the alert logs for each Contact Group on your account.
Bulk Update improvements
We’ve implemented a summary of which tests will be updated upon filtering for all Bulk Updates. This means that each time you run an update in bulk you’ll be able to see which tests were affected to the right side of the page.
UI Improvements
First off we’ve made some improvements to the screen which displays all of your tests, primarily the changes are contained within the “Box View” layout, we’ve changed the buttons on the test boxes to be smaller and more accessible, and we’ve ensured that all of the options for each test can be easily accessed without needing to drill down into the test’s details.
We’ve also somewhat standardized the entry system for the email addresses in the Contact Groups to closely match the phone number entry section.
This means now that it will not be possible to miss alerts due to formatting errors, all previous phone numbers have of course been ported over to the new system already!
API Limit Changes
Following user requests, we’ve increased the burst limit for our API to 20 per second, up from 10. To accommodate this change and also to prevent abuse in future we have elected to have a daily limit of 100,000 API calls per account – this is a level at which we can see that very few users will be affected, and we feel that it’s a fair limit in terms of using our API on any paid plan. There are no changes to this on the free level plan, and the same limit of 250 calls per day will apply.
StatusCake Team
Share this
More from StatusCake
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
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