Monitoring
Status Pages
Pricing
At StatusCake a large part of what we do is reacting to current downtime with alerts and logging historical downtime within reports. Today we’d like to take a look at how users can get the most out of customizing these factors.
On our Business level plan all alerts and reports via email can be fully customized to better represent your brand and ensure that the right information needed for your team to address issues quickly and efficiently is always present.
In the image below you can get an idea of the extent to which this is possible, all of our emails the get sent out can be modified as you see fit:
You can modify your alerts for Virus, Uptime, SSL, Domain, Page Speed, and Server type notifications in a range of different ways. Each template is managed individually and will apply to all notifications for the set type – you can also set test-specific changes up if there are tests that you’d rather not use the blanket default settings. For changes to all tests, you should go to the User Details section for setup, and for changes on an individual test level it’s just a case of editing the test in question and working with the three fields shown below:
When editing the email’s in the User Details section you’ll be able to change colors, logos, and even the base HTML/CSS of the email. We’ve included a range of tags which can be included in the code which will grab data which can make these emails more useful and tailored to your team.
| Tag | Usage |
|---|---|
| ||TITLE|| | Displays Test Name |
| ||SITE|| | Displays Website URL |
| ||TYPE|| | Displays Test Type (HTTP/PING/DNS etc) |
| ||QUOTE|| | TestID and alert number e.g ( 12345 – 1) |
| ||REASON|| | Display Cause of Downtime |
| ||TIME|| | Display total downtime length for test |
| ||HTTPCODE|| | Display the error Status Code |
| ||TESTID|| | Display the TestID on it’s own |
| ||CHECKRATE|| | Display how often the test is checked. |
| ||HOST|| | Display Hosting provider if present |
| ||CONFIRMEDTOTAL|| | Show Number of confirmations for downtime |
| ||MESSAGE|| | Display custom content set per test |
| ||TAGS|| | Include tags attributed to the test |
| ||VALID_FROM|| | Display the date from which the SSL certificate is valid (SSL only) |
| ||VALID_UNTIL|| | Display the date from which the SSL certificate is no longer valid (SSL only) |
So for example, you could populate the subject field of the alert email with these tags, something like “Your Site: ||TITLE|| Is Currently Down 533 ||REASON||”
Reports will work slightly differently in that they are showing a historic downtime record for one or more tests, we can fully edit these as well in terms of appearance, title, sender address and tags, and changes will apply both to automatically and manually generated reports.
We use a different set of tags here which can be seen in the table below, bear in mind that these are report specific and will not work for alert type notifications.
| Tag | Usage |
|---|---|
| ||CU|| | Display Total Uptime percentage for tests in report |
| ||WD|| | Display Number of Tests with downtime |
| ||WOD|| | Display Number of Tests with no downtime |
| ||TABLE|| | Display Table of Tests with downtime |
| ||UPTABLE|| | Display Table of Tests with no downtime |
If you’ve got questions on this or would like to know more, feel free to get in touch with our friendly support team who will gladly answer any questions you have!
Share this
4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes
3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and
3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests
3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect
7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and
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.
Find out everything you need to know in our new uptime monitoring whitepaper 2021
