Monitoring
Status Pages
Pricing
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
Share this
4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes
3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and
3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests
3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect
7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and
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.
Find out everything you need to know in our new uptime monitoring whitepaper 2021
