The use case: how Torq deploys incident.io
Torq replaced PagerDuty and an abandoned Rootly setup with incident.io to handle alert routing, on-call, Slack-based incident response, and postmortems in one standardized workflow across its engineering org.
More reported results
Figures published in incident.io’s case study. They are not independently measured by usedby.
100% post-incident follow-ups documented
In the customer’s words
When teams you didn't even plan to onboard are asking for access, you know something's working.Other AI tools used by Torq
Other public relationships recorded on usedby.
Explore Torq’s AI stackincident.io users in Cybersecurity
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
- Mar 26, 2026
- Last checked
- Nov 16, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 17 teamsChecked
Printed word for word on the page, near the name of Torq.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Torq.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Torq uses incident.ioChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Two months after switching to incident.io, PagerDuty & Rootly were gone, 17 teams were onboarded, and developers who had actively avoided the old setup were lining up to migrate.





