Monitoring
Status Pages
Pricing
It’s been a week now since we sent out our 4th customer survey and as always we’re not only noting down the responses but acting on them – our policy has always been we listen, we learn! It’s with this mind that today we’re happy to announce that we’ve made some improvements and changes to DNS monitoring.
You are now able to select the DNS server to use to performance the DNS check – this can either the DNS servers attached to your domain or alternatively any custom DNS servers you wish to input. You can set the DNS server to use by editing an existing DNS test or creating a new test.
With this change you can be certain that not only are your DNS servers pointing to the correct location but even more importantly that your DNS servers are up and responding in a timely manner.
Speaking of timely manners we’ve also changed how we record DNS response times. Previously when we used our own master DNS server we started recording response times from the point of connection – from now we will record them from the point of attempt at connection – because of this change you may see a small increase in your connection times, however this is a more realistic reflection of the load time.
A huge thanks to everyone who requested this improvement!
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
