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
Since we launched, having a big presence in the United States has been an important part of StatusCake website monitoring service.
We’ve grown our number of monitoring centers in the US over the last few months, so for those of you who haven’t checked our Knowledge Base or StatusCake News posts for a while you may not realize just how many monitoring centers we have.
We’ve also made some changes recently, switching from locations and servers which do not support iPv6 to ones that do. Helping us move towards our ambition of ensuring that our global network of website monitoring centers are all iPv6 fully compliant.
As part of this move we have, for now at least, shut down our San Jose monitoring center (it only supported iPv4) and added in a new monitoring center in Las Vegas. We now have six monitoring centers in the United States, all save for our second server in New York are fully iPv6 supported. Details of their IPs, so that you can white-list them, are provided below. You’ll find details of all our monitoring center’s in the Knowledge Base.
In order to select a monitoring center, rather than have our systems allocate a random center to you, you must be signed-up to one of our paid website monitoring plans. Premium plans start from just $4.99 (which will allow you to select two website monitoring centers from which your website’s uptime will be checked) – and if you sign-up for a year you’ll get two months absolutely free.
• United States, Vegas
IP: 209.141.61.87
• United States, New York
IP: 216.155.131.57
• United States, New York #2 (Not iPv6)
IP: 199.167.198.78
• United States, Dallas
IP: 199.168.100.248
• United States, Salt Lake City
IP: 68.169.44.43
• United States, New Jersey
IP: 108.61.49.187
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