otto

Status

Checked now, not claimed.

This page runs the site's own health checks in your browser when it loads — one request to the public /api/health endpoint, whose answers come from the services actually responding, not from a badge. The live check rows need JavaScript; with it off, the endpoint itself is still one request away and returns plain JSON anyone can read.

What it will not tell you

There is no historical uptime record behind this page yet, so it publishes no uptime percentage and no ninety-day chart — a number without measurement behind it would be marketing, not status. Incidents, when they happen, will be written here plainly: what broke, who was affected, what changed. None are recorded to date.

If something looks wrong right now, tell us — a person reads it.

This is a statement of our own practice, published so it can be checked against what we actually do. It is not legal advice and asserts nothing about anyone else's obligations. Where it is wrong or out of date, it is a defect in this document — tell us and it gets corrected here rather than quietly fixed.

About Otto

Otto publishes this reference and builds the software underneath it: case management for US creditor-side collections law firms, where a client's written rules run before an action is taken rather than in next month's report.