Skip to main content
usedby

As published on incident.io, June 2025. Captured by usedby on Oct 7, 2026.

What happened

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.

From the page. incident.io, captured Oct 7, 2026

What the story claims, and what we checked

We compared the story with its live page on Oct 7, 2026.

  • The passage quoted aboveCheckedCopied word for word from the page, near the name of Skyscanner.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • Skyscanner uses incident.ioCheckedConfirmed line. Latest check across sources: Oct 7, 2026.
  • The result itselfNot checkedWe quote it; we did not measure it.

Same company, same tool or same industry.

nearly 500projects monitored with SnykSkyscanner uses Snyk. Another tool at Skyscanner80%“Approximately 80% of our initial incident-response workflow is now automated.”Kaizen Gaming uses incident.io. Another customer of incident.ioUp to 10x“Up to 10x faster response time”Turbopuffer uses incident.io. Another customer of incident.io