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
We do hope that all our American users had a great Thanks-Giving, spending time with the family and those special to you!
We wanted to mark Thanks-Giving by seeing what we could do to improve the service for all of our customers across the world, not just those on the other side of the pond. So we’ve opened up two new monitoring centers in Salt Lake City and Dallas – in addition to the two already located in New York and San Jose. Salt Lake City becomes the first of our website monitoring center to be IPv6 supported; though during the next weeks and months we hope to have IPv6 across our entire monitoring network.
And unlike many of our competitors, with StatusCake you’re able to choose which server you want your website monitoring tested from. So wherever your business is based there’s always a monitoring center checking uptime and downtime that’s right for you.
So if you have a website, or visitors to your site from the UK, Holland, Singapore, Japan, Australia or the USA you will know exactly, using our real website browser experience, how a visitor from that part of the world views your website.
Whatever you’re doing this weekend you can rest assured that in the unfortunate situation that there’s any issue with your website you’ll be the first to know!
James Barnes
Share this
More from StatusCake
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026
When AI Speeds Up Change, Knowing First Becomes the Constraint
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
James Barnes
January 14, 2026
Make Your Engineering Processes Resilient. Not Your Opinions About AI
4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development. For some teams, it’s an obvious productivity multiplier. For others, it’s viewed with suspicion. A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes
James Barnes
January 8, 2026
Blog
How to monitor IPFS assets with StatusCake
3 min read IPFS is a game-changer for decentralised storage and the future of the web, but it still requires active monitoring to ensure everything runs smoothly.
Daniel
January 9, 2025