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 1 hr ago. Last stored result reached it in 282 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 11 | 0 | 0.0 | 154 ms | 0 |
| Mon 13 | 0 | 0.0 | 266 ms | 0 |
| Mon 15 | 0 | 0.0 | 150 ms | 0 |
| Mon 18 | 0 | 0.0 | 467 ms | 0 |
| Mon 20 | 0 | 0.0 | 423 ms | 0 |
| Mon 22 | 0 | 0.0 | 356 ms | 0 |
| Tue 00 | 0 | 0.0 | 301 ms | 0 |
| Tue 02 | 0 | 0.0 | 228 ms | 0 |
| Tue 04 | 0 | 0.0 | 351 ms | 0 |
| Tue 06 | 0 | 0.0 | 189 ms | 0 |
| Tue 08 | 0 | 0.0 | 294 ms | 0 |
| Tue 11 | 0 | 0.0 | 190 ms | 0 |
| Tue 13 | 0 | 0.0 | 208 ms | 0 |
| Tue 15 | 0 | 0.0 | 522 ms | 0 |
| Tue 17 | 0 | 0.0 | 180 ms | 0 |
| Tue 20 | 0 | 0.0 | 302 ms | 0 |
| Tue 22 | 0 | 0.0 | 390 ms | 0 |
| Wed 00 | 0 | 0.0 | 181 ms | 0 |
| Wed 02 | 0 | 0.0 | 254 ms | 0 |
| Wed 05 | 0 | 0.0 | 368 ms | 0 |
| Wed 07 | 0 | 0.0 | 314 ms | 0 |
| Wed 09 | 0 | 0.0 | 202 ms | 0 |
| Wed 11 | 0 | 0.0 | 286 ms | 0 |
| Wed 13 | 0 | 0.0 | 345 ms | 0 |
| Wed 16 | 0 | 0.0 | 141 ms | 0 |
| Wed 18 | 0 | 0.0 | 131 ms | 0 |
| Wed 20 | 0 | 0.0 | 107 ms | 0 |
| Wed 22 | 0 | 0.0 | 250 ms | 0 |
| Thu 00 | 0 | 0.0 | 399 ms | 0 |
| Thu 02 | 0 | 0.0 | 564 ms | 0 |
| Thu 05 | 0 | 0.0 | 100 ms | 0 |
| Thu 07 | 0 | 0.0 | 293 ms | 0 |
| Thu 09 | 0 | 0.0 | 78 ms | 0 |
| Thu 11 | 0 | 0.0 | 192 ms | 0 |
| Thu 13 | 0 | 0.0 | 305 ms | 0 |
| Thu 15 | 0 | 0.0 | 154 ms | 0 |
| Thu 17 | 0 | 0.0 | 360 ms | 0 |
| Thu 19 | 0 | 0.0 | 324 ms | 0 |
| Thu 21 | 0 | 0.0 | 83 ms | 0 |
| Thu 23 | 0 | 0.0 | 287 ms | 0 |
| Fri 01 | 0 | 0.0 | 84 ms | 0 |
| Fri 03 | 0 | 0.0 | 291 ms | 0 |
| Fri 05 | 0 | 0.0 | 540 ms | 0 |
| Fri 08 | 0 | 0.0 | 169 ms | 0 |
| Fri 10 | 0 | 0.0 | 211 ms | 0 |
| Fri 11 | 0 | 0.0 | 192 ms | 0 |
| Fri 13 | 0 | 0.0 | 91 ms | 0 |
| Fri 15 | 0 | 0.0 | 282 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Unthread 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 Unthread goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Unthread alerts to Slack, Discord or a webhook — free.
Unthread, at unthread.io, is one of the AI services we monitor. Unthread is an AI-native helpdesk for Slack and Microsoft Teams that automates ticketing, answers, knowledge, and workflows for IT, HR, customer support, and RevOps teams.
Unthread publishes an official status page at status.unthread.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 239 ms average, 70–540 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Unthread incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
239 ms on average over the last 24 hours (70–540 ms).
Yes, at https://status.unthread.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 Unthread here at once, the problem is on Unthread'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 Unthread. 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.