Torq Outage History
Torq is up right nowPingoru has recorded 51 incidents for Torq: 33 in the last 12 months and 4 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 5 | 25 of 720 (3%) |
| May 2026 | 4 | 6 of 744 (1%) |
| June 2026 | 4 | 6 of 720 (1%) |
| July 2026 | 1 | 3 of 744 (0%) |
| August 2026 | 1 | 65 of 744 (9%) |
| September 2026 | 2 | 5 of 720 (1%) |
| October 2026 | 1 | 6 of 536 (1%) |
Incidents, newest first
Notice October 8, 2026 [US] Small number of accelerated steps failing due to a Google Cloud incident 5h 46m Workflows Automation
Started Oct 08, 2026, 07:13 PM UTC· resolved Oct 09, 2026, 01:00 AM UTC
- monitoring Oct 08, 2026, 07:13 PM UTC
Since 12:10 UTC on October 8, a small number of accelerated steps in our US region have failed with a timeout error. The cause is an ongoing Google Cloud Storage incident in us-central1 that is slowing down uploads. Impact peaked between 15:30 and 17:10 UTC, fewer than 0.02% of accelerated steps failed. Most steps and workflows run normally. Google is working on a fix. We're monitoring it and will post an update when it's resolved or if the impact changes. Google's incident: https://status.cloud.google.com/incidents/mSFVt6PiP557bjRyYsut
- resolved Oct 09, 2026, 03:59 AM UTC
This incident has been resolved.
Minor September 2, 2026 Degraded Functionality in Case Editor 1h 14m Case Management
Started Sep 02, 2026, 03:50 PM UTC· resolved Sep 02, 2026, 05:04 PM UTC
- investigating Sep 02, 2026, 03:50 PM UTC
We're investigating a degradation in Case Editor functionality caused by a conflict with accessibility keyboard shortcuts. A fix is in progress — we'll update this page as we have more information.
- investigating Sep 02, 2026, 05:03 PM UTC
We are continuing to investigate this issue.
- resolved Sep 02, 2026, 05:04 PM UTC
This incident has been resolved.
Major September 1, 2026 [US] - Elevated error rates in US Data Center 3h 59m Workflows Automation, Administration Portal
Started Sep 01, 2026, 03:55 PM UTC· resolved Sep 01, 2026, 07:54 PM UTC
- identified Sep 01, 2026, 04:17 PM UTC
Elevated error rates in GCP us-central1 We have identified this as an upstream network issue with GCP: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev
- identified Sep 01, 2026, 04:17 PM UTC
We are continuing to monitor the issue
- monitoring Sep 01, 2026, 04:48 PM UTC
We are aware of a network service degradation affecting Google Cloud's us-central1-b zone, which began at approximately 15:20 UTC on September 1, 2026. Our infrastructure operates across multiple zones, and automated failover has moved affected workloads out of the impacted zone with no manual intervention required. Based on current information, impact was limited to approximately 15:20–16:00 UTC. Google reports the underlying network infrastructure has recovered and is validating individual service recovery. We are continuing to monitor Google Cloud's status page and will update this notice if anything changes. https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev
- monitoring Sep 01, 2026, 06:08 PM UTC
We continue to monitor Google Cloud's status updates regarding the network degradation in the us-central1-b zone. We are not seeing any impact on our side at this time. We will provide a further update once Google Cloud resolves the underlying incident.
- resolved Sep 01, 2026, 07:54 PM UTC
Google Cloud has resolved the network service degradation that affected a portion of the us-central1-b zone. Per Google's preliminary analysis, routine network fabric path maintenance triggered unexpected issues in one cluster in us-central1-b. Network capacity has been fully restored and all zonal and regional services are back to normal. Google has halted further maintenance in the region while they conduct proactive audits. https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev
Major August 22, 2026 [US] - Delayed Activity Log Ingestion 2d 16h Workflows Automation, Administration Portal
Started Aug 22, 2026, 04:06 AM UTC· resolved Aug 24, 2026, 08:54 PM UTC
- investigating Aug 22, 2026, 05:06 AM UTC
We are currently investigating delayed ingestion for activity logs. Some customers may experience a delay in activity log data appearing in the platform.
- investigating Aug 22, 2026, 06:28 AM UTC
We are continuing to investigate this issue.
- investigating Aug 22, 2026, 07:33 AM UTC
We are continuing to investigate this issue.
- identified Aug 22, 2026, 08:24 AM UTC
The issue has been identified and a fix is being implemented.
- identified Aug 22, 2026, 10:24 AM UTC
We are continuing to work on a fix for this issue.
- identified Aug 22, 2026, 12:37 PM UTC
We're aware of an issue affecting activity log ingestion, causing delays in log processing and failures when workflows attempt to attach events to cases. This is impacting a subset of customers in US data center. We're treating this as a top priority and working it with all hands on deck. We'll post the next update ASAP. We apologize for the disruption and appreciate your patience.
- identified Aug 22, 2026, 02:37 PM UTC
The backlog of activity log data has started being ingested, and we're seeing queue processing resume. Workflow event-attachment failures related to this issue should begin to ease as the backlog clears. We're continuing to monitor closely and will share a full ETA for complete resolution when possible. We appreciate your patience as we work through this.
- identified Aug 22, 2026, 04:39 PM UTC
The backlog queue continues to be ingested. Event-attachment to cases should start working again as processing catches up. We're currently working through the backlog for the last 10 hours of data. Known limitation: Older events (before the incident) are not currently visible in the UI while this backlog is processed. We'll continue to post updates as we make progress toward full resolution.
- monitoring Aug 22, 2026, 05:10 PM UTC
New executions are now showing up on the activity log. Backlog ingestion (last ~10 hours) is still in progress, and event-attachment to cases will work going forward from now on. We don't yet have an ETA for when backlog ingestion will finish or when older events will be visible in the UI. We'll share an ETA as soon as we have one. We'll continue posting updates until this is fully resolved.
- monitoring Aug 22, 2026, 07:51 PM UTC
* New executions are now showing up on the activity log. Backlog ingestion (last ~10 hours) is still in progress. * All Events JSON events are now shown in the activity log, though the associated execution may still be missing. * Execution logs in canvas are working and show full history for all steps. We'll update once we have an ETA for showing activity log data from before the incident. No events are lost — all activity logs will be restored. We'll continue posting updates until this is fully resolved.
- monitoring Aug 23, 2026, 02:57 PM UTC
Ongoing activity log events are being ingested as usual, with no performance impact. Activity log data from before the incident is still incomplete, and is being re-ingested. No data was lost during the incident. Another update will be made once we have an ETA for showing the incomplete data in the UI.
- monitoring Aug 24, 2026, 11:48 AM UTC
Ongoing activity log events are being ingested as usual, with no performance impact. Replicating historical Activity Log data from before the incident is still ongoing. No data was lost during the incident.
- resolved Aug 24, 2026, 08:54 PM UTC
We successfully replicated all activity log data starting on August 18th 00:00 (UTC) Activity log data replication continues until 90 days of data is available to query, which is expected in the coming days. As mentioned in former updates, live activity log data is ingested normally without issues Due to the above, we are marking this incident as resolved.
Minor July 9, 2026 [US] - Delays ingesting activity logs 3h 4m Administration Portal
Started Jul 09, 2026, 03:05 PM UTC· resolved Jul 09, 2026, 06:10 PM UTC
- investigating Jul 09, 2026, 03:05 PM UTC
We’re investigating slowness in activity log ingestion affecting some customers in the US Data Center. Some activity log events may be delayed by up to 10 minutes. This does not affect workflow automation. We’re working to restore normal processing speed and will provide an update as we learn more.
- investigating Jul 09, 2026, 03:49 PM UTC
We are continuing to investigate this issue.
- identified Jul 09, 2026, 04:31 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 09, 2026, 05:03 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jul 09, 2026, 05:08 PM UTC
We are continuing to monitor for any further issues.
- resolved Jul 09, 2026, 06:10 PM UTC
This incident has been resolved.
Notice June 25, 2026 [US] Intermittent login issues 1h 3m Administration Portal
Started Jun 25, 2026, 01:08 PM UTC· resolved Jun 25, 2026, 02:11 PM UTC
- monitoring Jun 25, 2026, 01:08 PM UTC
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.
- resolved Jun 25, 2026, 02:11 PM UTC
This incident has been resolved.
Minor June 23, 2026 Intermittent SSO login failures 2h 25m Administration Portal
Started Jun 23, 2026, 02:01 PM UTC· resolved Jun 23, 2026, 04:26 PM UTC
- investigating Jun 23, 2026, 02:01 PM UTC
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.
- monitoring Jun 23, 2026, 02:33 PM UTC
We identified an update to 3rd party security systems that block redirects to google identity.
Minor June 18, 2026 [US] Performance Issues: Intermittent errors loading Cases dashboards 1h 26m Administration Portal
Started Jun 18, 2026, 01:30 PM UTC· resolved Jun 18, 2026, 02:57 PM UTC
- investigating Jun 18, 2026, 01:37 PM UTC
We are currently investigating this issue.
- investigating Jun 18, 2026, 01:46 PM UTC
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.
- monitoring Jun 18, 2026, 02:02 PM UTC
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.
- resolved Jun 18, 2026, 02:57 PM UTC
This incident has been resolved.
Major June 18, 2026 [US] - Workflow executions experiencing degraded performance and missing step data in BuilderBox 1h Workflows Automation
Started Jun 18, 2026, 11:38 AM UTC· resolved Jun 18, 2026, 12:38 PM UTC
- investigating Jun 18, 2026, 11:38 AM UTC
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.
- investigating Jun 18, 2026, 11:50 AM UTC
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.
- identified Jun 18, 2026, 12:07 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 18, 2026, 12:25 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 18, 2026, 12:38 PM UTC
This incident has been resolved.
Notice May 27, 2026 [US] Delayed workflow executions 2h 2m Workflows Automation
Started May 27, 2026, 05:35 PM UTC· resolved May 27, 2026, 07:38 PM UTC
- monitoring May 27, 2026, 05:35 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 27, 2026, 07:38 PM UTC
This incident has been resolved.
Major May 21, 2026 [US] - Intermittent failures for Step Execution 2h 25m Workflows Automation
Started May 21, 2026, 02:26 PM UTC· resolved May 21, 2026, 04:52 PM UTC
- investigating May 21, 2026, 02:26 PM UTC
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.
- investigating May 21, 2026, 03:01 PM UTC
We are continuing to investigate this issue.
- investigating May 21, 2026, 03:08 PM UTC
We are investigating intermittent errors affecting workflows that use shared integrations in destination workspaces.
- identified May 21, 2026, 03:12 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 21, 2026, 03:30 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 21, 2026, 04:52 PM UTC
This incident has been resolved.
Minor May 19, 2026 [US] - Activity Log Events Delay 46m Administration Portal
Started May 19, 2026, 01:27 AM UTC· resolved May 19, 2026, 02:14 AM UTC
- identified May 19, 2026, 01:27 AM UTC
We are currently experiencing a degradation on the activity log. No impact to running executions or workflows.
- monitoring May 19, 2026, 01:36 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 19, 2026, 01:44 AM UTC
We are continuing to monitor for any further issues.
- resolved May 19, 2026, 02:14 AM UTC
This incident has been resolved.
Major May 4, 2026 API Authentication / Session Failures 17m Workflows Automation, Administration Portal
Started May 04, 2026, 11:53 AM UTC· resolved May 04, 2026, 12:11 PM UTC
- identified May 04, 2026, 11:53 AM UTC
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.
- monitoring May 04, 2026, 12:07 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 04, 2026, 12:07 PM UTC
We are continuing to monitor for any further issues.
- resolved May 04, 2026, 12:11 PM UTC
This incident has been resolved.
Minor April 15, 2026 [US] - Case Management search performance degradation 3h 33m Case Management
Started Apr 15, 2026, 01:55 PM UTC· resolved Apr 15, 2026, 05:28 PM UTC
- investigating Apr 15, 2026, 01:55 PM UTC
We are experiencing a slowness on case management UI Search
- monitoring Apr 15, 2026, 02:08 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 15, 2026, 05:28 PM UTC
This incident has been resolved.
Major April 12, 2026 [EU] - Cases Dashboard Data Ingestion - No New Data Since 10:00 UTC 7h 46m Administration Portal, Case Management
Started Apr 12, 2026, 10:00 AM UTC· resolved Apr 12, 2026, 05:47 PM UTC
- investigating Apr 12, 2026, 11:53 AM UTC
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.
- identified Apr 12, 2026, 12:05 PM UTC
We've identified the root cause Our engineering team is actively working on a fix.
- resolved Apr 12, 2026, 05:47 PM UTC
This incident has been resolved.
Minor April 11, 2026 [US] elevated latency during webhook ingest in US datacenter 1h 44m Workflows Automation
Started Apr 11, 2026, 05:53 AM UTC· resolved Apr 11, 2026, 07:38 AM UTC
- investigating Apr 11, 2026, 05:53 AM UTC
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.
- identified Apr 11, 2026, 06:25 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 11, 2026, 07:15 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 11, 2026, 07:38 AM UTC
This incident has been resolved.
Minor April 10, 2026 [US] Elevated executions error rate in US region 9h 55m Workflows Automation
Started Apr 10, 2026, 09:42 PM UTC· resolved Apr 11, 2026, 07:38 AM UTC
- investigating Apr 10, 2026, 09:42 PM UTC
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.
- monitoring Apr 10, 2026, 10:21 PM UTC
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.
- resolved Apr 11, 2026, 07:38 AM UTC
This incident has been resolved.
Minor March 20, 2026 Intermittent failures: Torq API Step Execution 4h 29m Workflows Automation
Started Mar 20, 2026, 05:51 PM UTC· resolved Mar 20, 2026, 10:20 PM UTC
- investigating Mar 20, 2026, 05:51 PM UTC
We are aware of intermittent failures affecting a subset of Torq API workflow steps. Cases are fully operational and unaffected.
- identified Mar 20, 2026, 06:53 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Mar 20, 2026, 10:13 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 20, 2026, 10:20 PM UTC
This incident has been resolved.
Critical March 12, 2026 Intermittent UI access issues 57m
Started Mar 12, 2026, 06:30 PM UTC· resolved Mar 12, 2026, 07:27 PM UTC
- monitoring Mar 12, 2026, 07:07 PM UTC
We have identified the root cause and are monitoring the fix
- resolved Mar 12, 2026, 07:27 PM UTC
This incident has been resolved.
Minor March 5, 2026 Slack integration degradation 4h 12m Slack Apps/Integrations
Started Mar 05, 2026, 09:40 PM UTC· resolved Mar 06, 2026, 01:53 AM UTC
- investigating Mar 05, 2026, 09:40 PM UTC
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.
- monitoring Mar 05, 2026, 09:40 PM UTC
We are actively monitoring Slack's internal status and will update as soon as their service stabilizes.
- resolved Mar 06, 2026, 01:53 AM UTC
This incident has been resolved.
Minor February 24, 2026 Service Degradation: Auditing Services 36m Administration Portal
Started Feb 24, 2026, 04:36 PM UTC· resolved Feb 24, 2026, 05:13 PM UTC
- investigating Feb 24, 2026, 04:36 PM UTC
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.
- monitoring Feb 24, 2026, 04:45 PM UTC
A fix has been implemented and we are monitoring the results
- resolved Feb 24, 2026, 05:13 PM UTC
The incident has been resolved
Minor February 2, 2026 [US] Slowness in step execution 3h 4m Workflows Automation
Started Feb 02, 2026, 04:19 PM UTC· resolved Feb 02, 2026, 07:23 PM UTC
- investigating Feb 02, 2026, 04:19 PM UTC
We're currently investigating step slowness affecting some users. Our team is actively working on a fix and we'll provide an update shortly.
- monitoring Feb 02, 2026, 05:17 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 02, 2026, 07:23 PM UTC
This incident has been resolved.
Minor February 2, 2026 [EU] Step execution failures 2h 34m Workflows Automation
Started Feb 02, 2026, 04:15 PM UTC· resolved Feb 02, 2026, 06:49 PM UTC
- investigating Feb 02, 2026, 04:15 PM UTC
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.
- monitoring Feb 02, 2026, 04:58 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 02, 2026, 06:49 PM UTC
This incident has been resolved.
Minor January 27, 2026 [EU+US] - Intermittent failures when searching for steps in the workflow builderbox 6h 20m Administration Portal
Started Jan 27, 2026, 11:15 AM UTC· resolved Jan 27, 2026, 05:35 PM UTC
- monitoring Jan 27, 2026, 04:55 PM UTC
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.
- monitoring Jan 27, 2026, 04:57 PM UTC
We've identified this is caused by an Azure OpenAI service disruption and are actively working on implementing a fallback solution.
- resolved Jan 27, 2026, 05:35 PM UTC
This incident has been resolved.
Minor January 5, 2026 [US] Degradation in Case management 1h 31m Workflows Automation, Case Management
Started Jan 05, 2026, 05:06 PM UTC· resolved Jan 05, 2026, 06:38 PM UTC
- investigating Jan 05, 2026, 05:06 PM UTC
We are currently investigating the issue.
- monitoring Jan 05, 2026, 05:57 PM UTC
A fix has been implemented and we are monitoring the results
- resolved Jan 05, 2026, 06:38 PM UTC
This incident has been resolved.