Is Moveworks down?

Last checked 10m ago
Current status
Moveworks has degraded performance

3 active incidents: Unable to send messages to the AI Assistant on MS Teams, Custom AI Assistant Logo Reverting to Moveworks Default (Mi… · +1 more

Official status page: https://status.moveworks.com · Polled every 5 minutes · 36 components tracked

Moveworks is reporting degraded performance right now (last checked 10m ago). Services are up but slower or partially failing.

Real-time Moveworks status, recent outages, and incident history — pulled directly from Moveworks's official status page at https://status.moveworks.com every 5 minutes. Pingoru tracks 36 Moveworks services and has captured 14 incidents in the last 90 days (99.21% uptime). Get email, Slack, Discord, or webhook alerts the moment Moveworks reports a new incident — free for 5 monitors, no credit card.

Users who monitor Moveworks also follow these APIs services: Vonage Make Vonage Business Retool Telnyx Mapbox Vonage API EasyPost Celigo Olo View all 6,000+ providers
Moveworks uptime 99.21% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Active incidents 3

  1. Ongoing ● 8d 22h
    Started Sep 04, 2026, 12:17 PM UTC
    Microsoft Teams
    Timeline · 2 updates
    • investigating · Sep 04, 2026, 12:17 PM UTC

      We have been seeing issues with a few users being unable to send messages to the Assistant on Teams. They see the chat bar being greyed out, which shows a message: "You cannot send messages to this bot". We are investigating the issue and are also working with Microsoft internally. At a high level, it looks like a policy update has blocked this bot from being accessible. We will keep you posted on the updates.

    • identified · Sep 04, 2026, 01:09 PM UTC

      Workaround Available We have identified that, for some affected customers, the Available to setting for the Moveworks bot in the Microsoft Teams admin centre is set to No one. Restoring the appropriate availability has resolved the issue for some customers. Teams administrators can update this setting by following these steps: 1. Sign in to the Microsoft Teams admin centre. 2. Go to Teams apps → Manage apps and select the Moveworks bot. 3. Open the Users and groups tab. Alternatively, select No one (org-wide default) if it appears as a link. 4. Under Availability, select Edit availability. 5. Change Available to from No one to one of the following: Everyone — Select this if all users in the tenant should have access to the bot. This is the most common setting for Moveworks deployments. Specific users or groups — Select this to restrict access to particular security groups, Microsoft 365 groups, dynamic membership groups, or distribution lists. Search for and add the required users or groups. 6. Select Apply to save the change. Microsoft advises that availability changes can take up to 24 hours to apply to all users and, in rare cases, up to six days to appear in the Teams client. However, the change may take effect sooner. After allowing sufficient time for propagation, affected users should completely sign out of Microsoft Teams and sign back in to refresh their access. We are continuing to investigate the underlying cause and will provide further updates as more information becomes available.

    Latest: Workaround Available We have identified that, for some affected customers, the Available to setting for the Moveworks bot in the Microsoft Teams admin centre is set to No one. Rest…

  2. Ongoing ● 24d 20h
    Started Aug 19, 2026, 02:21 PM UTC
    Microsoft Teams
    Timeline · 4 updates
    • identified · Aug 19, 2026, 02:21 PM UTC

      We're investigating an active issue where end users in Microsoft Teams are seeing the default Moveworks logo instead of their organization's custom bot logo, despite a custom icon being set in the app manifest. This appears to affect the bots published via the Teams App Store (store auth) rather than a single tenant. Logging out/back in or clearing the Teams cache resolves it for some users. Our engineering team is actively investigating and we will share more details as they become available.

    • identified · Aug 20, 2026, 12:10 AM UTC

      We have escalated this issue to Microsoft and are actively working with their team to address the issue. We will provide more details when they are available.

    • monitoring · Aug 20, 2026, 04:39 PM UTC

      Microsoft has identified the root cause as a platform regression affecting app branding display in Teams. A mitigation has been deployed and is currently rolling out. Microsoft's engineering team continues to monitor the rollout and validate the fix. Users may see the correct custom logo restored as the mitigation propagates. No action is required on your side. We will continue to monitor and will share additional updates as progress continues.

    • monitoring · Sep 01, 2026, 05:16 PM UTC

      Microsoft's mitigation continues to roll out and we are monitoring propagation. Most users should see the correct custom logo restored. If any users are still seeing the default Moveworks logo, please capture a HAR file while reproducing the issue and share it with Moveworks Support. We will share additional updates as progress continues.

    Latest: Microsoft's mitigation continues to roll out and we are monitoring propagation. Most users should see the correct custom logo restored. If any users are still seeing the default Mo…

  3. Ongoing ● 33d 20h
    Started Aug 10, 2026, 01:41 PM UTC
    Connectors
    Timeline · 1 update
    • identified · Aug 10, 2026, 01:41 PM UTC

      We have identified authentication failures affecting SharePoint Online integrations that use Microsoft App Store authentication, following Microsoft’s deprecation of the legacy ACS authentication method. As a result, legacy SharePoint knowledge ingestion will fail for affected customers. As an immediate workaround, please follow the SharePoint Online Azure App Registration guide. https://docs.moveworks.com/service-management/access-requirements/knowledge-base-systems/sharepoint-online-access-requirements-new-1#1-configure-azure-app-registration Engineering is working on a JWT-based update for Microsoft App Store authentication. We will share additional updates as they become available.

    Latest: We have identified authentication failures affecting SharePoint Online integrations that use Microsoft App Store authentication, following Microsoft’s deprecation of the legacy ACS…

Recent outages & incidents

Past 90 days
  1. Resolved 3h 30m
    Started Sep 10, 2026, 04:48 AM UTC · Resolved Sep 10, 2026, 08:19 AM UTC
    Moveworks SetupMoveworks DocumentationSupportCommunity
    Timeline · 3 updates
    • investigating · Sep 10, 2026, 04:48 AM UTC

      We are investigating an issue where users are not able to log in to the My Moveworks portal. We will keep you posted on the progress we make. We apologise for the inconvenience in the meantime.

    • monitoring · Sep 10, 2026, 05:27 AM UTC

      A fix has been implemented, and we are monitoring the results.

    • resolved · Sep 10, 2026, 08:19 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 1d 2h
    Started Aug 20, 2026, 02:55 PM UTC · Resolved Aug 21, 2026, 05:20 PM UTC
    Moveworks AI Assistant
    Timeline · 3 updates
    • investigating · Aug 20, 2026, 02:55 PM UTC

      We are seeing intermittent failures on outbound calls to Microsoft Teams, which may result in the Assistant not responding in Teams. There is currently an elevated volume of reported Microsoft Teams issues, and we are actively investigating whether this is the cause. Impact: Assistant messages in Microsoft Teams may intermittently fail to deliver, and users may not receive a reply. Impacted regions: All We will keep you posted with further updates.

    • monitoring · Aug 20, 2026, 02:58 PM UTC

      Error rates on outbound calls to Microsoft Teams are declining and the Assistant is responding normally for most requests. We are continuing to monitor to confirm full recovery.

    • resolved · Aug 21, 2026, 05:20 PM UTC

      The intermittent unresponsiveness of the AI Assistant in Microsoft Teams has been resolved. Responses have returned to normal, and we have confirmed stability through continued monitoring. No further action is required from customers.

    Latest: The intermittent unresponsiveness of the AI Assistant in Microsoft Teams has been resolved. Responses have returned to normal, and we have confirmed stability through continued mon…

  3. Resolved 20h 52m
    Started Aug 11, 2026, 05:45 PM UTC · Resolved Aug 12, 2026, 02:38 PM UTC
    Enterprise Approvals
    Timeline · 2 updates
    • monitoring · Aug 11, 2026, 05:45 PM UTC

      We identified an issue affecting multiple customers where approval requests were processed successfully, but users encountered a “You don’t have access to the request” error when retrieving the updated record. Engineering has deployed a fix and is currently monitoring the system to ensure stability. We will share additional updates as they become available.

    • resolved · Aug 12, 2026, 02:38 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 4h 47m
    Started Aug 10, 2026, 12:46 PM UTC · Resolved Aug 10, 2026, 05:33 PM UTC
    Moveworks Documentation
    Timeline · 3 updates
    • investigating · Aug 10, 2026, 12:46 PM UTC

      Our documentation site is currently down; we are working with the vendor to get it back up and running. We sincerely apologise for the inconvenience in the meantime.

    • monitoring · Aug 10, 2026, 12:53 PM UTC

      The fix has been implemented, the site is loading fine now, and we are continuing to monitor it.

    • resolved · Aug 10, 2026, 05:33 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved
    Started Aug 07, 2026, 11:57 AM UTC · Resolved Aug 03, 2026, 05:00 PM UTC
    Timeline · 1 update
    • resolved · Aug 07, 2026, 11:57 AM UTC

      We identified an issue with CSAT surveys not going out for the mentioned week. We identified the issue and have fixed it; subsequent CSAT's should run as usual. We sincerely apologise for the inconvenience caused.

    Latest: We identified an issue with CSAT surveys not going out for the mentioned week. We identified the issue and have fixed it; subsequent CSAT's should run as usual. We sincerely apolog…

See the full Moveworks outage history

9 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Moveworks outage history →

Or sign up free to get alerts when Moveworks breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 14 incidents View full outage history →