Live / Moveworks / Incident
Moveworks: Moveworks Assistant in Microsoft Teams Not Responding
Moveworks · moveworks.comCritical outageResolved2026-10-01 17:09 UTC
Public — what happened
Summary
Moveworks reported a critical problem with its Moveworks Assistant inside Microsoft Teams beginning at 15:20 UTC on 2026-10-01, with users seeing the bot appear to be working on a request but never replying. The company said it was looking for a way to mitigate the problem and did not name a cause in its updates. Moveworks said it applied a fix at 16:11 UTC and began watching the results, and it marked the incident resolved at 17:09.
Timeline
- Started — 2026-10-01 15:20 UTC
- Investigating — 2026-10-01 15:20 UTC (2 updates)
- Monitoring — 2026-10-01 16:11 UTC
- Resolved — 2026-10-01 17:09 UTC · 1h 48m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Moveworks against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Moveworks: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Moveworks report →
More from Moveworks
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.