Status and incidents
The status page is at status.tillcast.com. It is public and needs no sign-in. The dashboard links to it in its sidebar.
What the status page shows
Each service has its current state and its availability. The page opens with the last 7 days by the hour, and can show the last 30 or 90 days by the day.
- Printer connections. Whether printers can reach Tillcast. If the data for it is missing or old, the state is unknown and not operational.
- Printing. Whether a job goes through the whole path and is printed.
- Public API. Whether the API accepts a job and answers when it is read.
- Dashboard. Whether the dashboard answers.
Webhooks are planned and do not exist yet; a webhooks service joins the page when they do. Current and past incidents are listed with their updates. A state is the worse of what the checks measure and what an open incident says. If the checks have stopped, the page says “Unknown, data stale” and still shows an incident that was declared by a person.
How availability is measured
A canary sends a test job through the whole path every 5 minutes and confirms it as a real printer would. The job counts as printed when it was offered to the canary printer, downloaded and confirmed within 15 seconds, and the API then calls it printed. So the page shows whether printing works, not only whether a server answers.
The canary never declares an outage. Two failed checks in a row, about 10 minutes, set a service to degraded, and a person declares an incident. Announced maintenance counts as downtime.
Where it runs
The status page runs apart from the service, in another EU region, so that it stays up when the service is down.
What to do during an incident
- Check the status page first.
- When you ask for help, write to contact@tillcast.com and quote the
request_idfrom the error. See Errors.
See also Security and data.