Torq Outage History

Torq is up right now

Torq had 28 outages in the last 2 years totaling 6h 5m of downtime — averaging 1.2 incidents per month.

There were 28 Torq outages since June 11, 2025 totaling 6h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.torq.io

Minor June 30, 2025

[US] - Workspace Variable Service Disruption

Detected by Pingoru
Jun 30, 2025, 02:40 PM UTC
Resolved
Jun 30, 2025, 05:44 PM UTC
Duration
3h 4m
Affected: Workflows AutomationAdministration Portal
Timeline · 2 updates
  1. monitoring Jun 30, 2025, 03:28 PM UTC

    We experienced a service degradation affecting workspace variable operations that caused user errors and some execution failures between 14:40 UTC and 15:05 UTC. The issue has been fully resolved and all services are operating normally. We are investigating the root cause and continuing to monitor system stability.

  2. resolved Jun 30, 2025, 05:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 12, 2025

System Outage

Detected by Pingoru
Jun 12, 2025, 06:27 PM UTC
Resolved
Jun 12, 2025, 09:16 PM UTC
Duration
2h 49m
Affected: Workflows AutomationAdministration PortalCase Management
Timeline · 9 updates

Read the full incident report →

Notice June 11, 2025

Partial UI Outage

Detected by Pingoru
Jun 11, 2025, 09:03 AM UTC
Resolved
Jun 11, 2025, 09:14 AM UTC
Duration
11m
Affected: Administration Portal
Timeline · 3 updates
  1. investigating Jun 11, 2025, 09:03 AM UTC

    We are currently experiencing a partial UI outage affecting the Case Management section. Users may encounter issues viewing or interacting with certain case-related elements through the interface. This issue does not impact underlying workflows, case creation, or backend functionality. Our team is actively investigating the root cause and working to restore full functionality as quickly as possible. We will provide an update as soon as more information becomes available. Thank you for your patience.

  2. monitoring Jun 11, 2025, 09:08 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 11, 2025, 09:14 AM UTC

    This incident has been resolved.

Read the full incident report →