Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
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.
More Servers
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
Dedicated Test Speeds
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.
Better charting
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!
James Barnes
Share this
More from StatusCake
Turn StatusCake into a verified alerting and escalation flow with Hermes
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.
Daniel
May 13, 2026
Blog
Beyond Uptime: Building a Self-Healing OpenClaw Observability Stack
3 min read The allure of OpenClaw is undeniable. You deploy a highly autonomous, self-hosted AI agent, give it access to your repositories and inboxes, and watch it reason through complex workflows while you sleep. It is the dream of the ultimate 10x developer tool realized. But as any veteran DevOps engineer will tell you: running an LLM-backed
Daniel
April 23, 2026
When AWS us-east-1 Fails, Much of the Internet Fails With It
7 min read There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure,
James Barnes
April 15, 2026
In the Age of AI, Operational Memory Matters Most During Incidents
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
James Barnes
April 10, 2026
AI Didn’t Kill the SDLC. It Made It Harder to See
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
James Barnes
April 2, 2026
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026