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
New Zealand may only have a population of some 4.3 million people, but when it comes to e-Commerce it is no slouch. You only need to take a look at Creative HQ and The Icehouse – two world class incubators – to see that population size is no limit on creativity and ambition.
In Wellington the digital accelerator Lightning Lab showcased the first of nine startups from New Zealand and Australia earlier this year. These start-ups will be taken under the wing of 100 mentors, including Phil McCaw whose VC Movac invested in one of New Zealand’s best-known start-up success stories TradeMe.
Each of the start-ups – which include Teamisto and MyBuy in the nine chosen – received $18,000 NZD which all goes towards their big demo day on May 15th, some three weeks away, when they’ll all pitch their products to New Zealand’s VC and angel investor community.
With the domestic market relatively small most New Zealand eCommerce sites focus on the U.S as their target market – often using their home soil as a great opportunity to beta test their products and put them through the stresses of real customers. And with the U.S. a key market for New Zealand start-ups it is little surprise that the U.S. is often the exit for these businesses – Hyperfactory and M-Com being two great examples.
At StatusCake.com we’re looking to help great entrepreneurial businesses get going. And however big your website is, knowing that it is up and performing well is critical to your success. That’s why we’ve rolled out our first website monitoring centre in Auckland, New Zealand.
So whether you’re a New Zealand based online business with local customers or based overseas but have New Zealand customers, you’ll be able to have your website tested for downtime from a server that is most relevant to you. Because our New Zealand website monitoring is carried out from servers near you, rather than those thousands of miles away, you can be sure that we’re seeing what your New Zealand customers are seeing – and that load and response times are accurate.
The ability to choose our Auckland website monitoring centre to perform checks, or indeed any of global network of downtime monitoring servers, is available to all StatusCake paid plans customers, and if you pay for a year you’ll get two months absolutely free.
James Barnes
Share this
More from StatusCake
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
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