DownForAI

Dust.tt status: API, auth, latency & outage reports

Dust.tt is operational right now. DownForAI checks Dust.tt every ~75 minutes across 1 monitored surface, with 0 community reports in the last 24 hours.

Operational
Last probe 1h ago·1 surface
Probe-monitoredLow confidence
📚 Docs →💳 Pricing →
100.0%
24h Uptime
204ms
p50 Network Latency
486ms
p95 Network Latency
0
Incidents (30d)

DownForAI monitors Dust.tt via a single endpoint — Dust.tt Web. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 204 ms; p95: 486 ms.

No incidents have been logged for Dust.tt, and no community reports were received in the last 24 hours. Probes run continuously across the configured surfaces.

Data confidence: LowLast checked 1h 25m ago · 1 monitored surface · 1 with 24 h latency data

Current Status

Operational
Everything works normally
Checked by our probes · 176ms
Verified 1h ago
No major incident reported
No reports in the last 24h

Having issues?

Help other users by reporting if Dust.tt is not working for you.

0reports in the last 24 hours

Surface Health

Dust.tt WebOperational
HTTP 200p50 204ms1h ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about Dust.tt

No confirmed provider-side issue detected
DownForAI currently sees Dust.tt as operational based on available monitoring signals.
Signal source: public surface check · Monitoring confidence: Low
Still having trouble?

The issue may be account-specific, regional, network-related, or related to authentication, billing, quota, or rate limits.

Incident history (30d)

No incidents recorded in the past 30 days.

Reported symptoms

No user reports for Dust.tt in the last 24 hours.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

Dust is a platform for building custom AI assistants for teams, connected to company data (Notion, Slack, Google Drive, GitHub), on seat-based plans. Assistants run in Dust's cloud and depend on data-source syncs and model providers.

What we monitor
dust.tt web appAssistants and conversations
Data-source connectorsSyncs from connected tools
Model providersBehind assistants
Ecosystem dependencies
Notion, Slack, Google Drive, GitHub APIsModel providers

Fallback alternatives

What to use if this service is down

Dust is down
Relevance AI or Notion AI (monitored on DownForAI) can host custom assistants over company content
Major migration

How we monitor

DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.

Dust.tt statusEmbed this status badgeREADME · docs ▾
Markdown
[![Dust.tt status](https://downforai.com/api/badge/dust-tt.svg)](https://downforai.com/dust-tt)
HTML
<a href="https://downforai.com/dust-tt"><img src="https://downforai.com/api/badge/dust-tt.svg" alt="Dust.tt status" /></a>

Community Discussion

0/1000
No comments yet. Be the first to share your experience!

Still having issues with Dust.tt?

Let the community know and help others experiencing the same problem.