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’ve launched two new changes that will be beneficial to our users in the country of Denmark, you can read about what’s been added below:
New Copenhagen based monitoring servers
We’ve added several new monitoring servers to cover Denmark and these are based in the city of Copenhagen, all paid users will now be able to select this location when setting up a test – it’s as easy as selecting Europe -> Denmark/Copenhagen in the test’s settings.
We hope that users find the ability to test from this new location useful, and remember if there’s a location you need that we don’t have it’s always worth getting in touch via our live support to let us know!
New payment currency – Danish Krone
We know that pricing in US dollars isn’t great for everyone. First off with exchange rates in such flux nowadays, If the US dollar is strong it makes us more expensive.
Secondly, by being tied to another currency, it’s likely that you’re paying a slightly different amount each month, and third, maybe your debit or credit card company charges you a fee for making USD transactions.
We’ve made life simpler on this front recently by bringing in a wave of new payment currencies – and today we’re glad to announce that we will be introducing Danish Krone to enable our customers in Denmark to pay in their local currency! You’ll be able to pay in Danish Krone for our subscriptions on all terms, as well as additional SMS credits from here on in.
StatusCake Team
Share this
More from StatusCake
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
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