User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 20 min ago. Last stored result reached it in 157 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 328 ms | 0 |
| Mon 21 | 0 | 0.0 | 344 ms | 0 |
| Mon 23 | 0 | 0.0 | 269 ms | 0 |
| Tue 01 | 0 | 0.0 | 215 ms | 0 |
| Tue 04 | 0 | 0.0 | 304 ms | 0 |
| Tue 06 | 0 | 0.0 | 150 ms | 0 |
| Tue 08 | 0 | 0.0 | 320 ms | 0 |
| Tue 10 | 0 | 0.0 | 127 ms | 0 |
| Tue 12 | 0 | 0.0 | 334 ms | 0 |
| Tue 14 | 0 | 0.0 | 163 ms | 0 |
| Tue 17 | 0 | 0.0 | 149 ms | 0 |
| Tue 19 | 0 | 0.0 | 250 ms | 0 |
| Tue 21 | 0 | 0.0 | 135 ms | 0 |
| Tue 23 | 0 | 0.0 | 209 ms | 0 |
| Wed 02 | 0 | 0.0 | 265 ms | 0 |
| Wed 04 | 0 | 0.0 | 278 ms | 0 |
| Wed 06 | 0 | 0.0 | 249 ms | 0 |
| Wed 08 | 0 | 0.0 | 200 ms | 0 |
| Wed 11 | 0 | 0.0 | 188 ms | 0 |
| Wed 13 | 0 | 0.0 | 211 ms | 0 |
| Wed 15 | 0 | 0.0 | 220 ms | 0 |
| Wed 17 | 0 | 0.0 | 60 ms | 0 |
| Wed 19 | 0 | 0.0 | 194 ms | 0 |
| Wed 21 | 0 | 0.0 | 201 ms | 0 |
| Wed 22 | 0 | 0.0 | 213 ms | 0 |
| Thu 00 | 0 | 0.0 | 204 ms | 0 |
| Thu 02 | 0 | 0.0 | 152 ms | 0 |
| Thu 04 | 0 | 0.0 | 369 ms | 0 |
| Thu 06 | 0 | 0.0 | 165 ms | 0 |
| Thu 08 | 0 | 0.0 | 237 ms | 0 |
| Thu 10 | 0 | 0.0 | 336 ms | 0 |
| Thu 12 | 0 | 0.0 | 285 ms | 0 |
| Thu 14 | 0 | 0.0 | 95 ms | 0 |
| Thu 16 | 0 | 0.0 | 178 ms | 0 |
| Thu 19 | 0 | 0.0 | 174 ms | 0 |
| Thu 21 | 0 | 0.0 | 410 ms | 0 |
| Thu 23 | 0 | 0.0 | 342 ms | 0 |
| Fri 01 | 0 | 0.0 | 357 ms | 0 |
| Fri 03 | 0 | 0.0 | 183 ms | 0 |
| Fri 04 | 0 | 0.0 | 167 ms | 0 |
| Fri 06 | 0 | 0.0 | 333 ms | 0 |
| Fri 08 | 0 | 0.0 | 313 ms | 0 |
| Fri 10 | 0 | 0.0 | 125 ms | 0 |
| Fri 11 | 0 | 0.0 | 326 ms | 0 |
| Fri 13 | 0 | 0.0 | 167 ms | 0 |
| Fri 15 | 0 | 0.0 | 282 ms | 0 |
| Fri 17 | 0 | 0.0 | 158 ms | 0 |
| Fri 19 | 0 | 0.0 | 157 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Maintenance Window (US) - Data Infrastructure Upgrade
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…
Maintenance Window (EU) - Data Infrastructure Upgrade
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.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Torq yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Torq goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Torq alerts to Slack, Discord or a webhook — free.
Torq is listed in our AI category and checked at torq.io. The only end-to-end AI SOC Platform at enterprise scale. Scale SOC capacity while you triage, investigate, and respond to threats faster than ever. Get a demo.
Torq publishes an official status page at status.torq.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 246 ms average, 64–410 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Torq incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
246 ms on average over the last 24 hours (64–410 ms).
Yes, at https://status.torq.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Torq here at once, the problem is on Torq's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Torq. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.