Torq had 46 outages in the last 2 years totaling 77h 53m of downtime — averaging 1.9 incidents per month.
There were 46 Torq outages since September 19, 2024 totaling 77h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.
We've identified an issue affecting login via SSO and deployed a fix. We're now monitoring to confirm full resolution. Users may have experienced difficulty signing in; access should now be restored.
This incident has been resolved.
We are currently investigating reports of intermittent issues with Single Sign-On (SSO) login. Some users may be unable to log in and may need to refresh the page or retry to access their account. Not all users are affected. Our team is actively investigating the root cause. We will provide an update as soon as we have more information. We apologize for the inconvenience.
We identified an update to 3rd party security systems that block redirects to google identity.
We are currently investigating this issue.
Update: We continue to investigate the intermittent errors on the Cases dashboards. Performance is currently showing signs of improvement. The team is focused on identifying the root cause.
Root Cause Identified: We isolated the intermittent errors to an edge case within a specific query that triggered between 13:26 and 13:35 UTC. Mitigation: The underlying code path causing the issue has been disabled. Current Status: Errors have subsided, and we are continuing to monitor the dashboards to ensure stability.
This incident has been resolved.
We are currently investigating an issue with Builderbox where some workflow executions are experiencing degraded performance and failing to return step results. Our engineering team is actively looking into the root cause, and we will provide updates as more information becomes available. Affected region: US.
Identified - We have identified a potential root cause involving increased load on our database cluster and are currently working on a mitigation plan to restore normal performance levels. Some workflow executions may still experience delays or missing step data in BuilderBox in the interim. We will provide another update once the mitigation is underway.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating an increase in error rates affecting some steps in our workflow execution engine. A subset of user workflows may be experiencing failures or delays during step execution. We apologize for the disruption and will update this page as soon as we have additional details.
We are continuing to investigate this issue.
We are investigating intermittent errors affecting workflows that use shared integrations in destination workspaces.
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 experiencing a degradation on the activity log. No impact to running executions or workflows.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
A configuration change deployed at 13:56 IDT caused a significant drop in authentication and session success rates across key services. The problem was remediated on US and the team is now working on EU.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
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
We're currently investigating step slowness affecting some users. Our team is actively working on a fix and we'll provide an update shortly.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're currently investigating intermittent step execution failures affecting some users. Our team is actively working on a fix and we'll provide an update shortly.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating reports that step searches in the builder are not working What's happening: Some users are experiencing intermittent failures when searching for steps in the workflow builder. Some searches return errors instead of results. Impact: Step search functionality is experiencing intermittent errors in US and EU regions. Workaround: You can still add steps by manually browsing the step catalog, or retry the search. Status: We've identified this is caused by an Azure OpenAI service disruption and are actively working on implementing a fallback solution.
We've identified this is caused by an Azure OpenAI service disruption and are actively working on implementing a fallback solution.
This incident has been resolved.
We are currently investigating the issue.
A fix has been implemented and we are monitoring the results
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
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 experiencing an outage affecting the Torq Academy site. Users may be unable to access training materials, courses, or the Academy homepage.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We've identified that the slowness in non-accelerated steps is caused by an ongoing GCP incident. We are monitoring the situation closely and will provide updates as they become available.
This incident has been resolved
Current Status: We have identified an issue impacting customers in the AWS US-EAST-1 region where Interactions and some operators are failing to run. Root Cause: This is not an isolated issue with our platform. The disruption is attributed to a major, ongoing operational issue within the underlying cloud provider's infrastructure (AWS) that appears to be global in scope. Observed Impact: Any workflows with a Interactions are failing. Observed Scope: Multiple major services (e.g., Atlassian) are also impacted.
The disruption is attributed to a major, ongoing operational issue within the underlying cloud provider's infrastructure (AWS) that appears to be global in scope. See: https://health.aws.amazon.com/health/status
We're seeing improvement in Interactions and some operators. Schedule Triggers are still not operational. See: https://health.aws.amazon.com/health/status
We are starting to observe **signs of recovery** across the affected services.
Although we originally observed **signs of recovery** across the affected services, we have seen intermittent impacts to interacts, some operators, and third party services that you may have integrations with.
The affected services are showing improvement. We're maintaining close monitoring while AWS continues their remediation efforts. see: https://health.aws.amazon.com/health/status
We are continuing to monitor for any further issues.
This incident has been resolved.