TempoLife › Features › Service status › history
Incident history
Every recorded TempoLife incident, with what happened and when it was resolved. Nothing has been recorded yet.
No incidents have been recorded. That is a statement about the log, not a claim that nothing has ever gone wrong — the log starts when the first entry is written, and entries are written by hand.
What counts as an incident
Something that changed what the service did for the people using it: an endpoint returning errors, data that was wrong rather than missing, a deploy that broke a screen, a job that stopped running. Slowness counts when it was bad enough to be a failure in practice.
Routine deploys do not count. Neither does planned work that nobody noticed, and neither does a single failed probe that recovered by the next run — a blip in the check log is visible on the status board and does not need a story attached to it.
What each entry says
A title, the severity, when it started, when it was resolved, and a plain description of what happened. The description is written after the fact and is not edited to look better later. Where a fix shipped as a release, the entry says which one, so it can be checked against the changelog.
An incident with no resolution time is still open. Those sort to the top of this page and are repeated on the main status board, so an open problem is never something you have to go looking for.
Why the log is written by hand
Because an automated incident is a false claim in both directions. A five-minute probe interval turns a two-minute outage into silence, and a transient DNS failure at the prober turns a healthy service into a red block. The probe log is a measurement and lives on the board; an incident is an explanation and needs somebody to have understood what happened.
The cost of that choice is honest too: this list is only as complete as the discipline behind it. If an incident is missing, it is missing because nobody wrote it down, not because the system decided it did not count.
Source: TempoLife incident log (site_status_incidents) · checked 2026-09-02