There were 8 Torq outages since February 24, 2026 totaling 33h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are experiencing a slowness on case management UI Search
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We've identified that new data is not being ingested into the EU Cases Dashboard. Existing case data remains accessible, but no new cases are being added to the dashboards. Our team is actively working to identify and resolve the root cause. We'll provide updates as we progress.
We've identified the root cause Our engineering team is actively working on a fix.
This incident has been resolved.
We're currently investigating elevated latency during webhook ingest affecting multiple customers. Our team is actively working to identify and resolve the root cause. We'll provide updates as we progress.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating elevated error ("code": 9) rates affecting cloud runner steps. Our team is actively working to identify the root cause. Updates will be provided as they become available.
We've identified and cordoned off a faulty node in our GKE production cluster due to an underlying GCP infrastructure issue. We're working closely with GCP to identify the root cause and resolve the systemic problem with node health detection or automatic remediation.
This incident has been resolved.
We are aware of intermittent failures affecting a subset of Torq API workflow steps. Cases are fully operational and unaffected.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified the root cause and are monitoring the fix
This incident has been resolved.
We're aware of a degradation with our Slack integration that is preventing triggers from executing. While we are still receiving events from Slack, the slackbot is currently unable to dispatch automated triggers. We are actively monitoring Slack's internal status and will update as soon as their service stabilizes.
We are actively monitoring Slack's internal status and will update as soon as their service stabilizes.
This incident has been resolved.
We are currently investigating reports of performance degradation within our Auditing Services. Users may experience intermittent delays or slow response times while accessing audit logs and reports. Our engineering team is working to identify the root cause, and we are currently monitoring the situation to ensure service stability.
A fix has been implemented and we are monitoring the results
The incident has been resolved
Pingoru polls Torq's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required