Monitoring
Status Pages
Pricing
We recently sent out a customer survey and in which we asked users what they thought of every aspect of StatusCake – the single aspect which came in top in terms of marks was reliability and trustworthiness of alerts. It’s the core of our product so it makes sense that we want to get it right and as the survey showed it was clear we were hitting the nail on the head in almost all cases – but there was a niggling 2% of users who rated it under 5/5 and it’s only right we don’t ignore that.
Over the past few days we’ve been doing micro improvements to try to improve the speed of delivery for downtime alerts and this has manifested as a powerful set of improvements.
Firstly we’ve made changes to the Alert Trigger Rate. The vast majority of our users have set their trigger rate to be around 5 minutes ensuring they don’t get bothered about small periods of downtime, but what exactly happens at 5 minutes?
Previous to now your checks would continue on their normal check rate and upon each check the system would see if the current span between the point of downtime first detected to the current check was greater than trigger rate minutes then send out an alert. Sorry if that sounds confusing – it is! But we’ve simplified things to improve how quickly you get alerted – now when you have a 5 minute trigger rate you will get an alert on that 5th minute, no matter your check rate. As soon as your site is detected as down we will now check every 30 seconds until the trigger rate is hit – we’ll also check 20 seconds before your set trigger rate.
We’ve also introduced a better system for detecting the type of downtime and thus adjusting the confirmation servers as a result. If one system detects downtime as being content match then rather than just attempting once to see if the content match has failed on that test each confirmation server will take 3 attempts at loading the test, this way it’s much more likely to catch any downtime such as micro issues that only appear every so often.
I hope this helps explain a bit of the improvements we’ve rolled out today, but if I’m rambled on and make no sense I’ll summaries – we’ve got even better at sending alerts!
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
