The use case: how Trainline deploys incident.io
Trainline uses incident.io to run incident response and on-call in one platform, replacing separate Slack channels, PagerDuty, and a manual status page. It automates external communications, syncs service ownership from Backstage, and extends incident handling to lower severities and more teams.
More reported results
Figures published in incident.io’s case study. They are not independently measured by usedby.
20+ min saved per incident on external comms
1,200+ services synced daily from Backstage
Now when Trainline reorganizes (which they do regularly), the alert routing updates itself within 24 hours.
In the customer’s words
There are so many different use cases for incident.io. I don't envision us moving away anytime soon, if ever. I think it's here for the long haul.Other AI tools used by Trainline
Other public relationships recorded on usedby.
Explore Trainline’s AI stackincident.io users in Travel & Hospitality
Companies in the same sector, with public evidence.
See all incident.io customersGo straight to the source
Based on incident.io’s published case study. We check the public evidence; the results are reported by the vendor.
incident.io- Source published
- Jun 25, 2024
- Last checked
- Nov 22, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 3.5 hoursChecked
Printed word for word on the page, near the name of Trainline.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Trainline.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Trainline uses incident.ioChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Trainline produces a full Major Incident Report for every P1 and P2, a document that goes to the whole company in multiple formats. Historically, that took three to four hours per incident.




