Skip to main content
usedby
Search tools, companies

How Torq uses incident.io

17 teams

“17 teams were onboarded”

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

What happened

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.

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

When teams you didn't even plan to onboard are asking for access, you know something's working.

Nadav Baumer, DevOps Team Lead, Torq. Source, 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 figure: 17 teamsCheckedPrinted word for word on the page, near the name of Torq.
  • The passage quoted aboveCheckedCopied word for word from the page, near the name of Torq.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • Torq 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.

80%“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.io4+ hours“4+ hours saved on post-mortems”Built uses incident.io. Another customer of incident.io