Dust Outage History

44 incidents recorded over the last 365 days, 36 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Dust status100.00% uptime history

Every Recorded Dust Incident

Dust incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 12, 2026Dust API conversations and messages are slowThis incident has been resolved.1h 0mResolved
Sep 18, 2026Pods and conversations inaccessibleThis incident has been resolved.6 minResolved
Aug 24, 2026High latency on DustThis incident has been resolved.1h 29mResolved
Aug 24, 2026High latency on DustThis incident has been resolved.14 minResolved
Aug 18, 2026High latency on DustThis incident has been resolved.2h 18mResolved
Aug 11, 2026Agent executions fail with "The model is not supported"This incident has been resolved.44 minResolved
Jul 29, 2026High latency in Europe regionBack to normal1h 47mResolved
Jul 24, 2026Error when navigating DustThis incident has been resolved.4 minResolved
Jul 22, 2026Computer use unavailable in new conversationsThis incident has been resolved.5 minResolved
Jul 16, 2026Degraded performance of Dust platformThis incident has been resolved.2h 2mResolved
Jul 15, 2026Elevated Computer ErrorsThis incident has been resolved.20 minResolved
Jul 9, 2026Errors when agents read documents from connected data sourcesThis incident has been resolved.43 minResolved
Jun 25, 2026Computer unavailable in new conversationsThis incident has been resolved.11h 51mResolved
Jun 22, 2026Unable to send a messageUsers were unable to send a message for five minutes between 3:43pm to 3:47pm UTC. We identified the issues and the issue has been resolved.-26 minResolved
Jun 22, 2026Login failuresThis incident has been resolved.11 minResolved
May 31, 2026Scheduled maintenance of Dust.tt and api.dust.ttThe scheduled maintenance has been completed.1h 0mScheduled
May 24, 2026Scheduled maintenance of Dust.tt and api.dust.ttThe scheduled maintenance has been completed.1h 0mScheduled
May 12, 2026Dust API UnavailableThis incident has been resolved.-107 minResolved
May 7, 2026Elevated error rate on Google Gemini 3 modelsThis incident has been resolved.6h 27mResolved
May 6, 2026Elevated Errors on Anthropic's Sonnet 4.6This incident has been resolved.59 minResolved
May 5, 2026Degraded Search Performance in EUThis incident has been resolved44 minResolved
Apr 8, 2026Elevated Errors on Anthropic's Sonnet 4.6This incident has been resolved.2h 47mResolved
Mar 28, 2026Scheduled Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Mar 27, 2026Latency to be expected on interactions with agentsThis incident has been resolved.33 minResolved
Mar 18, 2026Latency to be expected on interactions with agentsThe incident has been resolved, a long term fix has been implemented and successfully rolled out.51 minResolved
Mar 16, 2026Dust EU Region unavailableBetween 00:00 UTC and 07:20 UTC today, EU users were unable to access Dust due to an expired TLS certificate. The Google-managed certificate for EU subdomains (eu.dust.tt, eu.connectors.dust.tt, eu.viz.dust.tt) failed…0 minResolved
Mar 7, 2026Scheduled Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Mar 2, 2026High latency in Europe regionThis incident has been resolved.45 minResolved
Feb 26, 2026Conversations processing errorsWe are continuing to monitor for any further issues.2h 27mResolved
Feb 17, 2026Increased latency on Dust Platform for some usersThis incident has been resolved.34 minResolved
Feb 11, 2026High latency on Dust ApplicationThis incident has been resolved.40 minResolved
Feb 11, 2026Agent responses are slower than normalThe latency spike have been mitigated. We are no longer receiving any reports of higher than normal agent response time4h 36mResolved
Feb 10, 2026Increased agent execution latencyIncident was resolved. We are investigating root cause to prevent reproduction.34 minResolved
Feb 6, 2026Agent responses are slower than normal;This incident has been resolved.51 minResolved
Jan 21, 2026Degraded performance on Dust interfaceResolved.52 minResolved
Jan 21, 2026Elevated Errors on Anthropic's Claude SonnetThis incident has been resolved.39 minResolved
Jan 15, 2026[EU] Unable to send messages.This incident has been resolved.1h 35mResolved
Dec 14, 2025[EUROPE] Scheduled Database Scaling MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Dec 12, 2025[EUROPE] Scheduled Database Scaling MaintenanceThe scheduled maintenance has been completed.30 minScheduled
Dec 12, 2025[EUROPE] Scheduled Database Scaling MaintenanceThe scheduled maintenance has been completed.30 minScheduled
Dec 5, 2025Login issues with DustOur provider is back online, incident resolved.30 minResolved
Nov 30, 2025Sign-In ErrorsThe DNS configuration issue impacting sign-in has been fully resolved. All authentication subdomains have been re-verified, and sign-in is now working normally for all users. Everything is operating as expected, and we…51 minResolved
Nov 29, 2025Scheduled Database Scaling MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Nov 24, 2025Websearch tool is not workingThe issue has been resolved, websearch is working.20 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Dust incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Dust Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Dust acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Dust outage in this window ran 11h 51m, against a mean recovery of 1h 22m. If you depend on Dust in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.