User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Emails to help@getthread.com are slow to process due to Microsoft outage
Source: the vendor's status page · We are not affiliated with Thread.
Estimated fix: Not enough Thread history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
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 1 hr ago. Last stored result reached it in 418 ms.
Minor incident
Emails to help@getthread.com are slow to process due to Microsoft outage Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 510 ms | 0 |
| Nov 7 | 0 | 0.0 | 525 ms | 0 |
| Nov 7 | 0 | 0.0 | 511 ms | 0 |
| Nov 7 | 0 | 0.0 | 421 ms | 0 |
| Nov 8 | 0 | 0.0 | 405 ms | 0 |
| Nov 8 | 0 | 0.0 | 488 ms | 0 |
| Nov 8 | 0 | 0.0 | 482 ms | 0 |
| Nov 8 | 0 | 0.0 | 497 ms | 0 |
| Nov 9 | 0 | 0.0 | 450 ms | 0 |
| Nov 9 | 0 | 0.0 | 514 ms | 0 |
| Nov 9 | 0 | 0.0 | 494 ms | 0 |
| Nov 9 | 0 | 0.0 | 546 ms | 0 |
| Nov 10 | 0 | 0.0 | 551 ms | 0 |
| Nov 10 | 0 | 0.0 | 508 ms | 0 |
| Nov 10 | 0 | 0.0 | 809 ms | 0 |
| Nov 10 | 0 | 0.0 | 532 ms | 0 |
| Nov 11 | 0 | 0.0 | 496 ms | 0 |
| Nov 11 | 0 | 0.0 | 516 ms | 0 |
| Nov 11 | 0 | 0.0 | 525 ms | 0 |
| Nov 11 | 0 | 0.0 | 557 ms | 0 |
| Nov 12 | 0 | 0.0 | 551 ms | 0 |
| Nov 12 | 0 | 0.0 | 451 ms | 0 |
| Nov 12 | 0 | 0.0 | 460 ms | 0 |
| Nov 12 | 0 | 0.0 | 430 ms | 0 |
| Nov 13 | 0 | 0.0 | 434 ms | 0 |
| Nov 13 | 0 | 0.0 | 384 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Thread 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 Thread goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Thread alerts to Slack, Discord or a webhook — free.
We track Thread (getthread.com) as part of the AI group. Thread is the AI service desk platform for MSPs, combining chat, AI triage, automation, and client intelligence to deliver faster support and scale modern service delivery.
Thread publishes an official status page at status.getthread.com; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 423 ms average, 316–532 ms range across 14 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Emails to help@getthread.com are slow to process due to Microsoft outage
We have not recorded a public Thread incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
423 ms on average over the last 24 hours (316–532 ms).
Yes, at https://status.getthread.com.
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 Thread here at once, the problem is on Thread'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 Thread. 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.