Is Torq down?

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.

We are continuing to investigate this issue.

This incident has been resolved.

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

We are continuing to monitor the issue

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

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.

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

We are currently investigating delayed ingestion for activity logs. Some customers may experience a delay in activity log data appearing in the platform.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

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.

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.

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.

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.

* 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.

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.

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.

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.

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.

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.

We are continuing to monitor for any further issues.

This incident has been resolved.

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.