Most status pages appear the week after the first bad outage. Ours is up before the first customer, empty, with the format already fixed — because a page created in a hurry is a page that gets to choose what it admits. If it happens, it goes here.
Current log
THIS COUNT GOES UP HONESTLY OR THE PAGE IS WORTHLESS
What every entry will contain
- Date and precise duration — start and end in UTC, not a vague 'brief period'.
- Severity, using the definitions below.
- Impact, in plain terms: who couldn't do what.
- Root cause, including when the cause was ours and when it was a provider's.
- Resolution and the follow-up change, if any.
How to read the severity labels
Full outage = every user couldn't use LADLE. Partial degradation = some subset of users affected, or one feature down while the rest worked. Elevated latency = the app worked but was slow. We publish a written post-mortem for any incident lasting more than 30 minutes.
Our commitment on timing
A service incident is logged here within 72 hours of resolution, including the ones that are embarrassing and the ones caused by a provider we chose. We are a very small team, so our honest commitment is 72 hours rather than the same-day promise a larger operation could make — but it is a real commitment, not a best effort.
REPORT AN ISSUE · HELLO@LADLE.CHAT
Related
Uptime figures (also not yet published — see why) live at /status/uptime-history. Security incidents are tracked separately at /security/incident-history, because they have a different disclosure obligation and a different clock.