# How Torq uses incident.io

**17 teams**: “17 teams were onboarded”

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

- Company: [Torq](https://www.usedby.ai/companies/torq.md)
- Tool: [incident.io](https://www.usedby.ai/tools/incident-io.md)
- Teams: engineering, field engineering, customer success

## What the story says

Torq replaced PagerDuty and an abandoned Rootly setup with incident.io to standardize incident response across its engineering org. Alerts are routed through incident.io, incidents run in Slack, and postmortems and action items are tied to the incident record.

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

> Two months into making the switch to incident.io, PagerDuty was gone. Teams that were never on the rollout plan were asking for access and developers who had actively avoided the previous setup were lining up to migrate.

> When teams you didn't even plan to onboard are asking for access, you know something's working.
>
> Nadav Baumer, DevOps Team Lead

## What usedby checked

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

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