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’d love to know what you’d like in an official StatusBoard Widget from StatusCake
We’re always huge fans of people who have a play around with the API and create something great – as the CTO here at StatusCake it always brings a huge smile to my face to discover something powered by our service. A wonderful user of ours called Dion recently built a widget for the popular (and awesome) Status Board iPad app. Status Board enables you to get an overview of all the data that is important to you – be it uptime data, performance data or the weather in London!
This is great for those who have a constant want to see the performance of your website in a nifty UI (and I’m afraid to say I suffer from this complexion) Status Board uses a simple enough coding language that enables you to get your data right inside the application by providing a formatted JSON result object – what Dion has done is taken our API and parsed the data and build a script to then echo it out into the format that Status Board expects. The script is coded in PHP and thus should be able to be run on pretty much all major servers and I can attest it works fantastically.
The full source code and guide can be grabbed from Dion’s site located here! As a thanks Dion we’ve upgraded your account for free to our business plan. As always if you have anything nifty to share then please do get in touch!
Daniel, C0-Founder StatusCake.com
UPDATE May 2017: StatusBoard announced that they would be closing down the app. If you’re looking for a dashboard to show your uptime monitoring stats then our very own StatusCake Dashboard feature is worth checking out. (Read More: How to Use the StatusCake Dashboards Feature)
James Barnes
Share this
More from StatusCake
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
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