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



We’ve just released a large update for the public reporting pages. This update adds several new features while also improving the overall design and usability of this popular feature.
You are now able to push live announcements on your public page. This announcements section allows you to add text about a current or historic downtime, explain the best channels of support or just introduce your public reporting page. You have full control over what to place in the announcements section and it supports a full range of customisations.
The public reporting pages we’re starting to look a little dated so we’ve brought the design up the modern standards and made the entire system responsive. We’ve also removed the need to page between pages to get more detailed information on each test – simply click an item in the table and the extended information will show. You are now also able to customise the colours in a greater degree of control.
If you want to only allow certain users to have access to your public reporting, then you are now able to password protect your page. Before any data is shown the end user must insert the password you set. This feature is for our paid users only.
We’ve also increased the overall speed of the public reports so that your visitors will be waiting less time in general.
Share this
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.
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
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,
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
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

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.
Find out everything you need to know in our new uptime monitoring whitepaper 2021