Monitoring
Status Pages
Pricing
Downtime happens, it’s a fact of running a website – but understanding and logging what caused the downtime enables you to better react in the future. It’s with this in mind that today we’re happy to announce the addition of annotation on downtime. You are now able to go to any one of your tests and click a period (be it a downtime period or uptime) and annotate that downtime. This means that you or a member of your team can quickly find out what caused each time down you have historical on your site.
To annotate a span simply go to your control panel, click a test and then click a span within the “Status Periods” section. You can then enter any information you want about this span.
Beyond being useful as a tool for internal use you can also optionally share your annotations on your public reporting page. This means you no longer need to have random spans of downtime without an explanation but rather you can inform users if it was scheduled or what caused it. You don’t have to share your annotations publicly but doing so will help build trust among your users.
It’s that simple!
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
