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
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
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026
When AI Speeds Up Change, Knowing First Becomes the Constraint
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
James Barnes
January 14, 2026
Make Your Engineering Processes Resilient. Not Your Opinions About AI
4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development. For some teams, it’s an obvious productivity multiplier. For others, it’s viewed with suspicion. A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes
James Barnes
January 8, 2026