Trainual Outage History
12 incidents recorded over the last 365 days, 9 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 Trainual Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 18, 2026 | Scheduled maintenance outageScheduled maintenance is currently in progress. We will provide updates as necessary. | 2h 0m | Scheduled |
| Sep 27, 2026 | Scheduled maintenance outageScheduled maintenance is currently in progress. We will provide updates as necessary. | 3h 0m | Scheduled |
| Aug 24, 2026 | Degraded performanceThis incident has been resolved. | 22 min | Resolved |
| Jul 23, 2026 | Elevated API errors and latencyThis incident has been resolved. | 2h 10m | Resolved |
| Jun 22, 2026 | Screen recorder unavailableThe upstream provider has released a fix for the API issue, and service has been restored. We have verified that affected functionality is operating normally and are resolving this incident. | 52h 50m | Resolved |
| Apr 17, 2026 | Degraded AI PerformanceWe have addressed the core issue and are discussing additional measures to ensure long term reliability. | 1h 8m | Resolved |
| Apr 6, 2026 | Issue with Embedded PDF PreviewsThis incident has been resolved. | 2h 58m | Resolved |
| Feb 23, 2026 | Service partially unavailableThis incident has been resolved. | 3h 12m | Resolved |
| Feb 20, 2026 | Web Application is downThis incident has been resolved. | 20 min | Resolved |
| Jan 27, 2026 | Degraded performanceThis incident has been resolved. | 2h 1m | Resolved |
| Jan 8, 2026 | Maintenance outageThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Nov 18, 2025 | Full Outage - Network issuesThis incident has been resolved. | 48 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Trainual incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Trainual 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 Trainual 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 Trainual outage in this window ran 2d 4h, against a mean recovery of 5h 59m. If you depend on Trainual 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.