# How Skyscanner uses incident.io

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

- Company: [Skyscanner](https://www.usedby.ai/companies/skyscanner.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: eng, dev, ops, data platform, employee enablement

## What the story says

Skyscanner replaced its in-house incident response workflow with incident.io to coordinate response to both internal and customer-facing incidents. Engineering and non-technical teams now use it to set up incident channels and follow guided, automated workflows.

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

> One of the unexpected benefits of switching over to incident.io is that we’ve managed to get different groups within our organization to manage incidents,” says Paris.

## What usedby checked

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

- Checked: the passage quoted above is copied word for word from the page, near the name of Skyscanner.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: Skyscanner 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/skyscanner-incident-io · How we check: https://www.usedby.ai/methodology