Torq logo

Is Torq Down?

SecurityLive status, outages, and incident history

No. Torq is up right now.

Every monitored Torq system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · every 60s

Know the moment Torq breaks

Torq is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Torq status page
How we know: the official Torq status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Torq Status Summary

As of 19:11 UTC on 14 November 2026, Torq is operational. PulsAPI checked Torq's official status page and found 4 of 4 components operational, with no active incidents. The latest incident, "[US+EU] Brief interruption loading Torq app", was on Nov 12, 2026 and lasted 0 min.

Cite as: PulsAPI, “Torq status”, checked 14 November 2026, 19:11 UTC. https://www.pulsapi.com/services/torq

Torq Component Status

The main Torq systems on this page. All 4 are operational right now.

4operational
Administration Portal
Operational
Case Management
Operational
Torq Learning Center
Operational

1 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Workflows Automation.

See all of them free

Component statuses may change independently during partial outages.

Recent Torq Outages & Incidents

Incident history from the official Torq status page, including resolution updates.

[US+EU] Brief interruption loading Torq appResolved Nov 12, 2026 · 0 minResolved

From 14:25 to 14:30 UTC, the Torq portal was unavailable. A small subset of Torq API related steps experienced failures The issue has been fixed and all services are currently operating normally. We apologize for the inconvenience.

[US] Small number of accelerated steps failing due to a Google Cloud incidentResolved Oct 8, 2026 · 5h 46mResolved

This incident has been resolved. --- [2026-10-08T19:13:52.428Z] (monitoring) 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

Degraded Functionality in Case EditorResolved Sep 2, 2026 · 1h 14mResolved

This incident has been resolved. --- [2026-09-02T17:03:22.878Z] (investigating) We are continuing to investigate this issue. --- [2026-09-02T15:50:03.679Z] (investigating) 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.

Upcoming maintenance

Announced by Torq. Planned work, not an outage.

Maintenance Window (US) - Data Infrastructure UpgradeScheduled for Nov 15, 2026 · 1h 0mScheduled

We will be performing routine infrastructure maintenance as part of ongoing improvements to ensure reliability and performance. During the maintenance: - Variables of type "table" will be temporarily unavailable in the Variables page (the page itself will remain accessible). - Table steps that start during the maintenance will show as running and will complete automatically once the maintenance is over. No executions will be lost. - Executions waiting on a table step count toward the workspace's concurrent execution limit, so in busy workspaces new executions may queue until the maintenance ends.

Maintenance Window (EU) - Data Infrastructure UpgradeScheduled for Nov 15, 2026 · 2h 0mScheduled

We will be performing backend maintenance on our database systems as part of our ongoing efforts to improve performance and reliability. No service impact is expected, and all systems should remain fully operational during this time.

Torq Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Torq incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Torq Outage Reports

Problems reported by engineers using Torq. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Torq problems reported yet.

Something wrong with Torq on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Torq

Is Torq down? Its official status page at status.torq.io reports on 4 components, including Administration Portal, Case Management and Torq Learning Center. PulsAPI checks it every few minutes and can alert you when Torq reports an incident.

Torq Status FAQ

Is Torq down right now?

The verdict at the top of this page comes from the latest poll of the official Torq status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Torq is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Torq recovers.

How do I check Torq uptime history?

PulsAPI tracks Torq uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Torq changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Torq outages?

PulsAPI reads the official Torq status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Torq components?

Yes. PulsAPI monitors 4 individual Torq components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Torq goes down?

Yes. Create a free account and subscribe to Torq: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Torq to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Torq problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Torq?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Torq plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Torq with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services