Monitoring
Status Pages
Pricing
Today we’re happy to announce we’ve made some big changes to our test servers which mean a range of small but noticeable improvements to both our free customers and our paid users, and to take advantage of this – improved charting.
We’ve rolled out an additional 10 servers (spread geographically) in the last week and these servers are already up and running. With these additional servers we now have over 80 running in operation querying sites at a rate of around 25,000 per a minute. This means each server is doing less work now and thus continuing to ensure no delays in testing
Previous to today we’ve always run free and paid tests in batches of around 250, each server testing 250 tests at any point of time, and each contending for the available bandwidth. We’ve now changed this so that each server is only running 20 tests at a time (thanks to the additional servers) and with a dedicated port speed of 250KB. This means you can better detect when performance is peeking and dropping as the charts will better reflect the reality of the load time.
Our performance charts always worked quite well but as we’ve started to get more and more data some users started to notice issues and or slow performance. This is because we used to store the data on performance in a MySQL table (a relic of the first version of StatusCake), it worked well when we had a few hundred tests running but now with over 250 million test results being added each week it was clear we needed to move data over; and that is exactly what we’ve done. Our performance data is now stored on a NoSQL (faster) database format, this means you will notice a lot less issues and a lot more speed! We will also be introducing exporting functionality now that we can query the data in a much faster way.
As always stay tuned for more updates coming your way!
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
