User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Thread down?
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.
What to try while Thread is having problems
Estimated fix: Not enough Thread history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
- Try the mobile app or a private window, or the API; another assistant can cover urgent work.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → getthread.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 371 ms.
Official status
Minor incident
Emails to help@getthread.com are slow to process due to Microsoft outage Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 04 | 0 | 0.0 | 507 ms | 0 |
| Mon 06 | 0 | 0.0 | 409 ms | 0 |
| Mon 08 | 0 | 0.0 | 558 ms | 0 |
| Mon 10 | 0 | 0.0 | 514 ms | 0 |
| Mon 12 | 0 | 0.0 | 387 ms | 0 |
| Mon 14 | 0 | 0.0 | 552 ms | 0 |
| Mon 16 | 0 | 0.0 | 494 ms | 0 |
| Mon 18 | 0 | 0.0 | 546 ms | 0 |
| Mon 20 | 0 | 0.0 | 519 ms | 0 |
| Mon 23 | 0 | 0.0 | 552 ms | 0 |
| Tue 01 | 0 | 0.0 | 506 ms | 0 |
| Tue 03 | 0 | 0.0 | 560 ms | 0 |
| Tue 05 | 0 | 0.0 | 551 ms | 0 |
| Tue 07 | 0 | 0.0 | 420 ms | 0 |
| Tue 09 | 0 | 0.0 | 569 ms | 0 |
| Tue 11 | 0 | 0.0 | 508 ms | 0 |
| Tue 13 | 0 | 0.0 | 912 ms | 0 |
| Tue 16 | 0 | 0.0 | 706 ms | 0 |
| Tue 18 | 0 | 0.0 | 637 ms | 0 |
| Tue 20 | 0 | 0.0 | 511 ms | 0 |
| Tue 22 | 0 | 0.0 | 532 ms | 0 |
| Wed 01 | 0 | 0.0 | 696 ms | 0 |
| Wed 03 | 0 | 0.0 | 593 ms | 0 |
| Wed 05 | 0 | 0.0 | 426 ms | 0 |
| Wed 07 | 0 | 0.0 | 505 ms | 0 |
| Wed 10 | 0 | 0.0 | 526 ms | 0 |
| Wed 12 | 0 | 0.0 | 525 ms | 0 |
| Wed 14 | 0 | 0.0 | 572 ms | 0 |
| Wed 16 | 0 | 0.0 | 505 ms | 0 |
| Wed 18 | 0 | 0.0 | 557 ms | 0 |
| Wed 20 | 0 | 0.0 | 489 ms | 0 |
| Wed 23 | 0 | 0.0 | 572 ms | 0 |
| Thu 01 | 0 | 0.0 | 460 ms | 0 |
| Thu 03 | 0 | 0.0 | 551 ms | 0 |
| Thu 05 | 0 | 0.0 | 575 ms | 0 |
| Thu 07 | 0 | 0.0 | 655 ms | 0 |
| Thu 09 | 0 | 0.0 | 451 ms | 0 |
| Thu 11 | 0 | 0.0 | 437 ms | 0 |
| Thu 13 | 0 | 0.0 | 416 ms | 0 |
| Thu 15 | 0 | 0.0 | 532 ms | 0 |
| Thu 17 | 0 | 0.0 | 460 ms | 0 |
| Thu 19 | 0 | 0.0 | 457 ms | 0 |
| Thu 21 | 0 | 0.0 | 430 ms | 0 |
| Thu 23 | 0 | 0.0 | 372 ms | 0 |
| Fri 01 | 0 | 0.0 | 316 ms | 0 |
| Fri 04 | 0 | 0.0 | 506 ms | 0 |
| Fri 05 | 0 | 0.0 | 434 ms | 0 |
| Fri 07 | 0 | 0.0 | 371 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Thread badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Thread yet. Outages of 10 minutes or more get their own page here.
Having trouble with Thread?
One report per service every 10 minutes from this network. No account.
Follow Thread
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.
About Thread
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: 430 ms average, 316–532 ms range across 11 successful checks.
Questions
Is Thread down right now?
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
When was Thread last down?
We have not recorded a public Thread incident since monitoring began 8 days ago.
What is Thread's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Thread respond?
430 ms on average over the last 24 hours (316–532 ms).
Does Thread have an official status page?
Yes, at https://status.getthread.com.
Thread not working for me but the status is fine. What now?
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.