Monitoring
Status Pages
Pricing
How does the monitor, monitor the monitor? No it’s not a tongue twister, but rather a question we faced when StatusCake started to be joined by big companies such as the BBC, NHS, EA to name but a few.
StatusCake now monitors over 250,000 websites and has tens of thousands of users who rely on it to let them know if their site goes down. If StatusCake were to face difficulties, it would impact our users on a grand scale delaying their alerts and missing downtime – so it’s clear we needed a good monitoring system.
StatusCake was built around the principals of easily deployable nodes that can come up and down without impacting service quality. We have a high level of redundancy with around 50% of our node servers able to go down at any one point without impacting check rates or alert quality at all. Each node is independent of each other, and each grabs a workload and holds the entire systems workload on it at any one time. Using this independent structure, if a node were to be unable to connect to the master servers it continues on and tests servers that have been assigned to it. To ensure tests are not duplicated among servers they each talk to each other letting each server know which servers are having trouble and what work load to take because of that.
So that reduces the possibilities of something going wrong to an extreme level and means we can use StatusCake to monitor StatusCake. We have a StatusCake account that is set up for us that monitors all our servers, even the HTTP server! If any part of StatusCake were to go down another part would notify us almost instantly. We don’t believe in over redundancy when it comes to offering our users the insurances that their monitoring will remain in place, no matter the difficulties that may arise.
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
