Truto Outage History
2 incidents recorded over the last 365 days, 2 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Truto Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 16, 2026 | APIs are down | 929h 27m | Resolved |
| Apr 20, 2026 | truto.one/docs is down | 1714h 6m | Resolved |
How to Read This Truto Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Truto acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Truto outage in this window ran 71d 10h, against a mean recovery of 55d 1h. If you depend on Truto in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.