Status
Availability is reported on a separate host, monitored from outside our infrastructure. A status page served from the thing it is reporting on is not a status page.
Where it lives
status.cosend.app, driven by an external uptime monitor that
runs outside our hosting and is unaffected by anything that takes our hosting down.
It is not live yet. The monitor goes up with the API, before public launch. This page names the host rather than linking it, because a link that 404s on the page you visit to find out whether something is broken is worse than no link.
What is checked
- api.cosend.app
- The Runtime API, /v1 and webhook ingress. Checked at its health endpoint, which reports on the database and the job queue behind it rather than only on the process being up.
- app.cosend.app
- The dashboard and the shared inbox.
- mcp.cosend.app
- The MCP server.
The checks run from outside, against the public hostname, which is the only kind of check that can tell you the difference between “the service is down” and “the service cannot tell you it is down”.
The target, and why it is not higher
99.5%. A higher target would look better here and it is not one we have built. The database and the API both run on managed platforms we do not control, and that is the trade we made for having no servers to administer — it is on the security page and in the Terms in the same words.
A published target we miss is worse than a modest one we beat. When the architecture justifies a higher number, the number moves.
Incidents get posted, including the short ones
On this architecture, at this target, there will be incidents. The difference between a customer who tolerates one and a customer who leaves is almost always whether they heard about it from us or found it in their own logs.
So every incident is posted, with what broke, what it affected, and what was done about it — including the forty-minute ones nobody would have noticed. A status page with no history reads as a status page nobody updates, and that is the impression it will correctly be giving.
Something broken and not posted yet? [email protected].