StatusCake

CNAME Your Public Reporting Page

website monitoring

The StatusCake.com public reporting pages are a great way to let the world know how great your website uptime is – and it’s these public reporting pages which we have spent some time working on recently. We know from feedback that people don’t like the fact that they have to use the StatusCake domain to show their public reporting page.  So we’re happy to announce that from today you are now able to setup CNAMEs for public reporting pages.

How to set up CNAME

To setup a CNAME just point your domain to uptime.statuscake.com . Once you have pointed your domain you can go into the Users tab within your StatusCake website monitoring account and type the domain you wish to use.

Beyond the ability to use a CNAME for public reporting pages we’ve also spruced up the overall design and usability of the public reporting pages – and we’ve got a lot more coming soon (including the ability to privately share). Traditional non-CNAME’ed public reporting will remain in the old style into migration later this month (once all features are ported).

At StatusCake we’re always looking for all feedback and feature requests for the new public reporting page so please do get in touch via email, Twitter or Live Chat!

Share this

More from StatusCake

What the Namecheap Outage Revealed About DNS Recovery

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

Monzo’s Stand-In Held Up on Wednesday. Some Customers Still Had a Bad Day.

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

What Broke GitHub on August 17 and How Retries Made the Incident Worse

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

Automate StatusCake Monitoring with viaSocket

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

Website Monitoring Checklist: What to Track Beyond Uptime

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

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

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.