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
It’s been about 5 months since we first launched our Weekly, Daily and Monthly Email Reports and in most regards it’s been a huge success with thousands of reports being sent out every day – but here at StatusCake we’re not the type to rest on our laurels. Today I’d like to introduce some changes we’re making to the reports.
Sleek New Design
We know looks aren’t everything, but they help! With this in mind we’ve introduced a brand new look which we hope will start to create a much more unified feel to the outbound emails we sent. We’ve also removed all remote images from the reports so you don’t need to enable remote content to be able to tell what sites are up and which are down, instead we’re relying on a simple colour coded system.
Separated Data
In the previous version of the public reports we gave you a long table of all your sites with no separation, this meant that you had to spend time trying to find tests with less than perfect uptime. With the new reports your tests are divided into ‘With Downtime’ and ‘Without Downtime’ so you can quickly get the information you need.
Global Uptime
We’ve also added in Global Uptime so you can see the uptime of your tests combined, this along with other key stats can be found at the top of the report.
Delivery Improvements
Previously our system sent all the reports in one big bulk, this in turn meant that the actual time you received your report fluctuated widely and we understand some users simply never received the reports at all. With the new reports we’re now running these reports in a batch system to ensure that you get your report around the same time every time – (roughly to the minute!) this means you can easily compare like for like on previous reports.
James Barnes
Share this
More from StatusCake
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
Alert Noise Isn’t an Accident — It’s a Design Decision
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.
James Barnes
February 4, 2026