User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 18 min ago. Last stored result reached it in 324 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 195 ms | 0 |
| Mon 20 | 0 | 0.0 | 123 ms | 0 |
| Mon 22 | 0 | 0.0 | 158 ms | 0 |
| Tue 00 | 0 | 0.0 | 438 ms | 0 |
| Tue 02 | 0 | 0.0 | 155 ms | 0 |
| Tue 04 | 0 | 0.0 | 368 ms | 0 |
| Tue 07 | 0 | 0.0 | 263 ms | 0 |
| Tue 09 | 0 | 0.0 | 142 ms | 0 |
| Tue 11 | 0 | 0.0 | 127 ms | 0 |
| Tue 13 | 0 | 0.0 | 345 ms | 0 |
| Tue 15 | 0 | 0.0 | 200 ms | 0 |
| Tue 17 | 0 | 0.0 | 138 ms | 0 |
| Tue 20 | 0 | 0.0 | 380 ms | 0 |
| Tue 22 | 0 | 0.0 | 230 ms | 0 |
| Wed 00 | 0 | 0.0 | 374 ms | 0 |
| Wed 02 | 0 | 0.0 | 165 ms | 0 |
| Wed 05 | 0 | 0.0 | 370 ms | 0 |
| Wed 07 | 0 | 0.0 | 97 ms | 0 |
| Wed 09 | 0 | 0.0 | 211 ms | 0 |
| Wed 11 | 0 | 0.0 | 389 ms | 0 |
| Wed 14 | 0 | 0.0 | 145 ms | 0 |
| Wed 16 | 0 | 0.0 | 380 ms | 0 |
| Wed 18 | 0 | 0.0 | 142 ms | 0 |
| Wed 20 | 0 | 0.0 | 122 ms | 0 |
| Wed 22 | 0 | 0.0 | 215 ms | 0 |
| Thu 00 | 0 | 0.0 | 330 ms | 0 |
| Thu 02 | 0 | 0.0 | 302 ms | 0 |
| Thu 04 | 0 | 0.0 | 354 ms | 0 |
| Thu 06 | 0 | 0.0 | 135 ms | 0 |
| Thu 09 | 0 | 0.0 | 167 ms | 0 |
| Thu 11 | 0 | 0.0 | 306 ms | 0 |
| Thu 13 | 0 | 0.0 | 123 ms | 0 |
| Thu 15 | 0 | 0.0 | 394 ms | 0 |
| Thu 17 | 0 | 0.0 | 158 ms | 0 |
| Thu 19 | 0 | 0.0 | 199 ms | 0 |
| Thu 21 | 0 | 0.0 | 201 ms | 0 |
| Thu 23 | 0 | 0.0 | 136 ms | 0 |
| Fri 01 | 0 | 0.0 | 647 ms | 0 |
| Fri 03 | 0 | 0.0 | 376 ms | 0 |
| Fri 05 | 0 | 0.0 | 355 ms | 0 |
| Fri 07 | 0 | 0.0 | 175 ms | 0 |
| Fri 09 | 0 | 0.0 | 340 ms | 0 |
| Fri 11 | 0 | 0.0 | 358 ms | 0 |
| Fri 13 | 0 | 0.0 | 113 ms | 0 |
| Fri 15 | 0 | 0.0 | 318 ms | 0 |
| Fri 17 | 0 | 0.0 | 107 ms | 0 |
| Fri 19 | 0 | 0.0 | 170 ms | 0 |
| Fri 20 | 0 | 0.0 | 324 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 Dust 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 Dust goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Dust alerts to Slack, Discord or a webhook — free.
Dust, at dust.tt, is one of the Productivity services we monitor. Dust connects your company knowledge, tools, and teams so you can create, share, and run agents across real workflows. Use different models for different tasks, with people in control.
Dust publishes an official status page at status.dust.tt; when we can read it, its incident level is folded into the status shown here.
Typical issues with productivity services: files not syncing, editors not loading, and sign-in problems.
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: 278 ms average, 107–647 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Dust incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
278 ms on average over the last 24 hours (107–647 ms).
Yes, at https://status.dust.tt.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Dust here at once, the problem is on Dust'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 Dust. 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.