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
Today we have released our new reporting tool which can be used to send out automated email reports for Uptime, SSL, Domain, and Virus type tests.
If you want to get stuck in right away, the new email reporting functions can be found within the User Details section of the StatusCake app. Here you can manage reports that you have created previously, and add new ones.
All reports can be automated to go out at the time of your choice on a daily, weekly or monthly basis. Each report can contain it’s own sub-set of email contacts making it easy to ensure that the right data is going to the right people.
With this new functionality it’s possible for the first time to create a report combining the details of your Uptime, Domain, SSL and Virus scan tests in the same report making it much easier to see trends over the different methods of testing.
Within the report the Uptime type tests will have data on the percentage of downtime experienced during the reported period, as well as average load time. For Domains and SSL you will be able to view any upcoming expiry dates that need your attention, and for the Virus Scan you will see a summary of any threats that have been detected since the last report.
For anyone who set up automated reports with our previous reporting function – rest assured that these reports will still be sent as normal, the settings for these can still be modified at any time within the User Details section of the app.
StatusCake Team
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