# How Trainline uses incident.io

**3.5 hours**: “3.5 hours saved per P1/P2 post-mortem”

As published on [incident.io](https://incident.io/customers/trainline), June 2024. Captured by usedby on 2026-10-07.

- Company: [Trainline](https://www.usedby.ai/companies/trainline.md)
- Tool: [incident.io](https://www.usedby.ai/tools/incident-io.md)
- Industry: [Travel & Hospitality](https://www.usedby.ai/companies/industry/travel-hospitality.md)
- Teams: Security, Data, Engineering

## What the story says

Trainline consolidated its fragmented incident management tooling into incident.io for incident response and on-call, replacing PagerDuty. It uses Workflows to automate external communications, status pages, and AI-assisted post-mortems, and syncs its Backstage service catalog so alert routing follows organizational changes.

Summary written by usedby from the source page, in English. The figures are those of incident.io and Trainline, not ours.

> 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.

- **20+**: “20+ min saved per incident on external comms”
- **1,200+**: “1,200+ services synced daily from Backstage”

> 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.
>
> Dan

## What usedby checked

We compared the story with its live page on 2026-10-07.

- Checked: the figure 3.5 hours is printed word for word on the page, near the name of Trainline.
- Checked: the passage quoted above is copied word for word from the page, near the name of Trainline.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: Trainline uses incident.io. Confirmed line. Latest check across sources: 2026-10-07.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/trainline-incident-io · How we check: https://www.usedby.ai/methodology