Status page
Measured uptime, per service. Not a number somebody typed in.
One line that says whether you are up, and the times underneath that prove somebody is awake.
When you go down, your inbox goes up.
Everybody writes at once, and every one of them asks the same thing: is it just me? Answering forty of those by hand is the worst possible use of the hour you need for fixing it — and each one is a person you have already kept waiting.
Uploads are failing
What it does
The banner is the page
One line, one colour, readable from across a room. Almost every visit lands on a day when nothing is wrong, so the page is built for that day rather than the rare one.
The worst thing wins
Two incidents open, one minor and one major, and the banner says major. It cannot quietly average itself back to green while something is still broken.
Times, not just words
Every update is stamped and kept. "We are looking into it" written once at 09:35 reads as abandonment; the same sentence with two more an hour apart reads as somebody working.
Green comes back on its own
Set the incident to Resolved and the banner returns to green by itself. There is no second switch to remember on the day you least want one.
An unrecognised word is not good news
States are matched leniently, in your language as well as ours, and anything unrecognised counts as ongoing. A green badge over a broken product is a far worse failure than an amber one over a working product.
History is the argument
Past incidents stay on the page. A status page with nothing ever recorded on it is not reassuring — it is evidence that nobody writes anything down.
Four ways it shows up
On the ordinary day
Green, with the last incident under it as proof the page is a real one.
Uploads are failing
On the bad one
The banner names what is broken. Nobody reads three paragraphs to find out.
Uploads are failing
The timeline
Every update kept, with the time on it. That is what says you are still there.
Uploads are failing
- Monitoring10:46
Uploads are succeeding again. Watching for half an hour.
- Identified10:09
A storage node was returning errors. Taking it out of rotation.
- Investigating09:35
We are seeing failed uploads and are looking into it.
Back to green, by itself
Resolve the incident and the banner follows. There is nothing else to switch off.
Uploads are failing
Fair questions
Isn't this just a page I could write myself?+
You could, and then you would be editing HTML in the middle of an outage — exactly when you have no attention to spare. Here it is a state, a body and a timestamped line, and the banner follows from them.
What if my status page goes down with everything else?+
It is hosted here rather than on your own infrastructure, and public pages are served from a cache rather than the database. Staying up on the day yours does not is the entire point of it.
Adding it
One script tag on the page you want it, or a link to the page we host. Both come with every widget.
<div id="changelog"></div>
<script src="http://localhost:3000/embed/your-slug" data-target="#changelog" async></script>Your product moved this week. Your website should say so.
Set up the first widget in a few minutes and put it live today.