Moveworks Outage History

Moveworks is up right now

Moveworks had 49 outages in the last 2 years totaling 4192h 16m of downtime — averaging 2 incidents per month.

There were 49 Moveworks outages since June 9, 2025 totaling 4192h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.moveworks.com

Major June 11, 2026

Enterprise Search Unavailable in AI Assistant — Resolved

Detected by Pingoru
Jun 11, 2026, 12:30 AM UTC
Resolved
Jun 11, 2026, 12:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Jun 11, 2026, 02:31 AM UTC

    On June 10, 2026, between 5:15 PM and 6:24 PM PST, users in the US region experienced a loss of Enterprise Search within the AI Assistant. Our team identified and resolved the issue within the same hour. We apologize for the impact to your experience.

Read the full incident report →

Critical June 9, 2026

MyMoveworks Access Issue

Detected by Pingoru
Jun 09, 2026, 01:03 PM UTC
Resolved
Jun 09, 2026, 02:52 PM UTC
Duration
1h 48m
Affected: Moveworks SetupMoveworks DocumentationSupportCommunity
Timeline · 4 updates
  1. investigating Jun 09, 2026, 01:03 PM UTC

    We are currently investigating an issue that is preventing users from accessing the My Moveworks Portal. Our team is actively working to identify the root cause and restore full functionality as quickly as possible. We apologize for the inconvenience and will provide updates as our investigation progresses.

  2. identified Jun 09, 2026, 01:27 PM UTC

    We have identified the issue and are currently working on deploying a fix. We will provide another update once the fix has been applied.

  3. monitoring Jun 09, 2026, 01:34 PM UTC

    We have successfully applied a fix and confirmed that the My Moveworks Portal is loading as expected. We will continue to monitor to ensure full stability is maintained. Thank you for your patience.

  4. resolved Jun 09, 2026, 02:52 PM UTC

    This incident has been resolved as of 6:30 AM PST. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor June 5, 2026

AI Assistant Answers Degradation

Detected by Pingoru
Jun 05, 2026, 01:08 PM UTC
Resolved
Jun 05, 2026, 02:59 PM UTC
Duration
1h 51m
Affected: Answers
Timeline · 4 updates
  1. investigating Jun 05, 2026, 01:08 PM UTC

    We are currently investigating an issue where the assistant is not serving answers from knowledge articles. We will provide updates as the investigation progresses.

  2. identified Jun 05, 2026, 01:32 PM UTC

    We are seeing some improvement, but failures are still occurring. We are actively working on a fix and will continue to provide updates.

  3. monitoring Jun 05, 2026, 02:26 PM UTC

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

  4. resolved Jun 05, 2026, 02:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 20, 2026

View permission feature in Setup is erroring out

Detected by Pingoru
May 20, 2026, 12:28 PM UTC
Resolved
May 20, 2026, 02:06 PM UTC
Duration
1h 37m
Affected: Moveworks Setup
Timeline · 2 updates
  1. identified May 20, 2026, 12:28 PM UTC

    We have identified an issue where the **View Permission** feature in Setup is currently returning an error instead of the expected results. Our team is actively working on a fix and will keep you updated on the progress. We apologise for the inconvenience caused and appreciate your patience in the meantime.

  2. resolved May 20, 2026, 02:06 PM UTC

    We are pleased to inform you that the issue with the View Permission feature in Setup has been resolved. The feature is now returning the expected results. We apologize for the inconvenience caused and thank you for your patience.

Read the full incident report →

Minor May 19, 2026

User Identity Ingestion Failures

Detected by Pingoru
May 19, 2026, 04:42 PM UTC
Resolved
May 19, 2026, 08:06 PM UTC
Duration
3h 24m
Affected: Moveworks AI Assistant
Timeline · 3 updates
  1. identified May 19, 2026, 04:42 PM UTC

    We are currently investigating an issue affecting User Identity Ingestion. Impacted customers may experience failures in user identity sync, which could affect AI Assistant access to new users dependent on up to date user data. Our engineering team has been engaged and is actively working toward a resolution. We will provide updates as more information becomes available.

  2. identified May 19, 2026, 05:51 PM UTC

    We are continuing to investigate the issue affecting User Identity Ingestion. Our engineering team has identified that the failure occurs during the identity validation step when processing geocode information of users. Work is actively ongoing to resolve this. We will provide another update as soon as more information is available.

  3. resolved May 19, 2026, 08:06 PM UTC

    This incident has been resolved. User Identity Ingestion is now functioning as expected and user identity sync has been restored for all affected customers. We apologize for any inconvenience this may have caused.

Read the full incident report →

Critical May 12, 2026

Live Agent Chat Degradation

Detected by Pingoru
May 12, 2026, 08:35 PM UTC
Resolved
May 12, 2026, 08:55 PM UTC
Duration
19m
Affected: Live Agent Message Brokering
Timeline · 2 updates
  1. identified May 12, 2026, 08:35 PM UTC

    We have identified an issue where Live Agent Chat is not functioning for some users. Affected users are unable to be handed off to a live agent and may encounter an error when attempting to do so. We apologize for the inconvenience and are actively working to resolve this. Updates will be provided as they become available.

  2. resolved May 12, 2026, 08:55 PM UTC

    This incident has been resolved as of 1:45 PM PST. Live Agent Chat has been restored and is functioning as expected. We appreciate your patience and apologize for any inconvenience caused.

Read the full incident report →

Major April 22, 2026

Embedded AI Assistant Degradation

Detected by Pingoru
Apr 22, 2026, 04:43 PM UTC
Resolved
Apr 22, 2026, 05:44 PM UTC
Duration
1h
Affected: Embedded AI Assistant
Timeline · 3 updates
  1. investigating Apr 22, 2026, 04:43 PM UTC

    We are actively investigating an issue where some users are not seeing the Moveworks Embedded AI Assistant loading on their employee service portals or intranet sites. We appreciate your patience and will provide updates as our investigation progresses.

  2. identified Apr 22, 2026, 05:07 PM UTC

    We have identified the issue and are currently pushing a fix. We will monitor closely and provide a further update once confirmed resolved. We appreciate your patience.

  3. resolved Apr 22, 2026, 05:44 PM UTC

    We are pleased to confirm that the issue causing the Moveworks AI Assistant to not load on web pages has been fully resolved. We appreciate your patience and apologize for any inconvenience this may have caused.

Read the full incident report →

Critical March 24, 2026

AI Assistant Outage on Microsoft Teams

Detected by Pingoru
Mar 24, 2026, 04:45 PM UTC
Resolved
Mar 24, 2026, 08:31 PM UTC
Duration
3h 45m
Affected: Microsoft Teams
Timeline · 8 updates
  1. investigating Mar 24, 2026, 04:45 PM UTC

    We have identified an issue where users are currently unable to chat with the AI Assistant on Microsoft Teams. Our team is actively investigating the root cause and working to resolve this as quickly as possible. We appreciate your patience and will share updates as soon as more information becomes available.

  2. investigating Mar 24, 2026, 05:08 PM UTC

    We currently suspect this may be related to a Microsoft Teams issue and are actively working with Microsoft to help drive resolution. We appreciate your patience and will share updates as soon as more information becomes available

  3. identified Mar 24, 2026, 05:27 PM UTC

    Microsoft has now published a Service Health Advisory (TM1260604) related to this issue. We are continuing to monitor updates from Microsoft and will share further information as it becomes available. Please follow the Microsoft Service Health Advisory (TM1260604) for the latest updates and progress on resolution via the Microsoft 365 Service Health dashboard. We appreciate your patience and will share updates as soon as more information becomes available

  4. identified Mar 24, 2026, 05:55 PM UTC

    Microsoft has shared that their monitoring has detected an increase in failures when users attempt to interact with bots. They are currently analyzing these failures to better understand the issue and determine next steps toward identifying the root cause. We appreciate your continued patience as Microsoft investigates and works toward resolution.

  5. identified Mar 24, 2026, 06:34 PM UTC

    Microsoft continues to actively work on this issue. Please follow the Service Health Advisory (TM1260604) for the most up to date information and progress toward resolution.

  6. identified Mar 24, 2026, 07:02 PM UTC

    Microsoft’s initial findings indicate that a portion of the infrastructure supporting bots in Microsoft Teams is operating in a degraded state. They are attempting to restart affected components and redirect traffic to healthy infrastructure to help mitigate the issue.

  7. monitoring Mar 24, 2026, 07:42 PM UTC

    Based on our recent testing, the AI Assistant on Microsoft Teams is now functioning as expected. We will continue to closely monitor the situation and provide further updates if needed. We appreciate your continued patience as the situation stabilizes.

  8. resolved Mar 24, 2026, 08:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 18, 2026

AI Assistant Unresponsive in Microsoft Teams (App Store)

Detected by Pingoru
Mar 18, 2026, 04:40 PM UTC
Resolved
Mar 18, 2026, 05:50 PM UTC
Duration
1h 10m
Affected: Microsoft Teams
Timeline · 4 updates
  1. identified Mar 18, 2026, 04:40 PM UTC

    We have identified an issue where the AI Assistant in the Microsoft Teams App Store is not responding to users. Our team is actively investigating and working to resolve this as quickly as possible. We appreciate your patience and will share updates as soon as more information becomes available

  2. identified Mar 18, 2026, 05:08 PM UTC

    We have identified the root cause of the issue and are currently in the process of deploying a fix. Our team is actively pushing the necessary changes to restore full functionality for affected users. We will provide another update once the deployment is complete. Thank you for your continued patience.

  3. monitoring Mar 18, 2026, 05:23 PM UTC

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

  4. resolved Mar 18, 2026, 05:50 PM UTC

    We’re pleased to confirm that the issue has been resolved. Thank you for your patience and continued support.

Read the full incident report →

Major March 17, 2026

AI Assistant Outage

Detected by Pingoru
Mar 17, 2026, 08:11 PM UTC
Resolved
Mar 17, 2026, 06:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Mar 17, 2026, 08:11 PM UTC

    We identified and resolved an issue where some users experienced failed or missing responses while interacting with the Moveworks AI Assistant. During this time, the assistant may have been temporarily unresponsive or slower than expected. Our team quickly investigated the issue and implemented mitigations to restore normal service. We sincerely apologize for the inconvenience and appreciate your patience. Duration: 11:19 PM – 11:36 PM PST

Read the full incident report →

Critical February 19, 2026

AI Assistant Outage in Gov Cloud

Detected by Pingoru
Feb 19, 2026, 04:40 PM UTC
Resolved
Feb 19, 2026, 04:45 PM UTC
Duration
5m
Affected: Moveworks AI Assistant
Timeline · 2 updates
  1. identified Feb 19, 2026, 04:40 PM UTC

    We’re aware that some users may be experiencing difficulties accessing the AI Assistant in Gov Cloud. Our engineering team is actively investigating the issue and working on a resolution. We’ll provide updates as more information becomes available and appreciate your patience while we work to restore full service.

  2. resolved Feb 19, 2026, 04:45 PM UTC

    This incident has been resolved

Read the full incident report →

Minor February 12, 2026

Microsoft Teams Degradation

Detected by Pingoru
Feb 12, 2026, 04:26 AM UTC
Resolved
Feb 12, 2026, 08:17 AM UTC
Duration
3h 50m
Affected: Microsoft Teams
Timeline · 4 updates
  1. investigating Feb 12, 2026, 04:26 AM UTC

    We are currently investigating an issue affecting some users who are unable to chat with the Moveworks AI Assistant in Microsoft Teams, although the bot remains reachable in other platforms. Customers are still receiving employee communications and notifications from the bot. We are actively working on a resolution and we will keep you posted with updates as we learn more. We sincerely apologize for the inconvenience caused.

  2. identified Feb 12, 2026, 05:25 AM UTC

    We have received acknowledgment of the issue from Microsoft and are actively collaborating with them to resolve it. We will share further updates as we have more information.

  3. monitoring Feb 12, 2026, 06:12 AM UTC

    A fix has been implemented by Microsoft for the issue, we are continuing to monitor the results.

  4. resolved Feb 12, 2026, 08:17 AM UTC

    This incident has been resolved. The Service Health Advisory that you can look up in your M365 Admin center Service Health section is TM1230990.

Read the full incident report →

Major February 4, 2026

Issues with AI Assistant responses

Detected by Pingoru
Feb 04, 2026, 12:17 PM UTC
Resolved
Feb 04, 2026, 02:51 PM UTC
Duration
2h 33m
Affected: Moveworks AI Assistant
Timeline · 5 updates
  1. monitoring Feb 04, 2026, 12:17 PM UTC

    We noticed an issue where some users were experiencing delays in the response and few users did not get any response from the Assistant at all. We have put in a fix for the same and are monitoring the results.

  2. monitoring Feb 04, 2026, 01:35 PM UTC

    At this time, we are still noticing some intermittent slowness, and our team continues to work on fully resolving the issue. We will provide further updates as soon as possible.

  3. monitoring Feb 04, 2026, 02:04 PM UTC

    We appreciate your patience as our engineering team remains fully engaged and focused on restoring consistent performance. We will continue to monitor the situation closely and provide another update as more information becomes available. Thank you for your ongoing patience.

  4. monitoring Feb 04, 2026, 02:19 PM UTC

    We have applied some fixes and are seeing improvements in the performance. We will continue to monitor the situation closely and provide another update as more information becomes available. We appreciate your patience and thank you for your ongoing support.

  5. resolved Feb 04, 2026, 02:51 PM UTC

    This incident has been resolved as of 6:12 AM PST. We appreciate your patience.

Read the full incident report →

Minor January 28, 2026

Notification Delays via AI Assistant

Detected by Pingoru
Jan 28, 2026, 04:19 PM UTC
Resolved
Jan 28, 2026, 08:40 PM UTC
Duration
4h 20m
Affected: ConciergeTriageEmployee Communications
Timeline · 3 updates
  1. investigating Jan 28, 2026, 04:19 PM UTC

    We are currently investigating an issue where some users may be experiencing delays in notifications through the AI Assistant. This may impact ticketing, triage, employee comms, and other notifications. Our team is actively working to identify the root cause and restore full functionality as quickly as possible. We sincerely apologize for the inconvenience and appreciate your patience. We will provide updates as more information becomes available. Thank you for your understanding.

  2. monitoring Jan 28, 2026, 06:14 PM UTC

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

  3. resolved Jan 28, 2026, 08:40 PM UTC

    This incident has been resolved. Thanks again for you patience and understanding.

Read the full incident report →

Major January 21, 2026

SSO Login Issue Affecting My Moveworks Portal

Detected by Pingoru
Jan 21, 2026, 04:46 PM UTC
Resolved
Jan 21, 2026, 06:02 PM UTC
Duration
1h 16m
Affected: Paths WorkspaceMoveworks SetupQueries WorkspaceMoveworks DocumentationEvents WorkspaceSupportPlugins WorkspaceCommunity
Timeline · 4 updates
  1. identified Jan 21, 2026, 04:46 PM UTC

    We have identified an issue preventing users from signing in to the My Moveworks portal. This appears to be affecting customers who use Ping Identity for authentication. We sincerely apologize for the inconvenience and are actively working to resolve the issue. We will provide updates as more information becomes available.

  2. identified Jan 21, 2026, 05:04 PM UTC

    We are now also observing that this issue is impacting customers using non Ping Identity SSO providers as well. Our engineering teams are continuing to investigate and remediate the root cause.

  3. monitoring Jan 21, 2026, 05:15 PM UTC

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

  4. resolved Jan 21, 2026, 06:02 PM UTC

    The issue has been fully resolved, and users should now be able to sign in to the My Moveworks portal using SSO normally. If you continue to experience problems, please contact support.

Read the full incident report →

Notice January 16, 2026

FAQ's not serving.

Detected by Pingoru
Jan 16, 2026, 06:57 AM UTC
Resolved
Jan 15, 2026, 01:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Jan 16, 2026, 06:57 AM UTC

    We saw an issue around FAQ's not being served for users, we identified this issue and it stands fixed now.

Read the full incident report →

Minor December 30, 2025

Intermittent Ticket Submission Failures

Detected by Pingoru
Dec 30, 2025, 09:35 PM UTC
Resolved
Dec 31, 2025, 02:00 AM UTC
Duration
4h 24m
Affected: Concierge
Timeline · 2 updates
  1. identified Dec 30, 2025, 09:35 PM UTC

    We have identified an issue that is impacting some customers during ticket creation: although tickets are being created successfully, the process is failing when we attempt to fetch the ticket, resulting in the error “Unsupported Ticket type for reference ID …” and preventing the submission from completing. We apologize for the inconvenience this is causing, and our team is actively working on a fix to restore normal ticketing functionality as quickly as possible. Impacted Regions: US, EU, CA, AU

  2. resolved Dec 31, 2025, 02:00 AM UTC

    Our engineering team has deployed a hot fix to resolve the issue affecting ticket submissions. The incident should now be resolved. We appreciate your patience and apologize for the inconvenience.

Read the full incident report →

Notice December 18, 2025

Agent Studio Notify action Degradation

Detected by Pingoru
Dec 18, 2025, 05:43 AM UTC
Resolved
Dec 17, 2025, 06:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Dec 18, 2025, 05:43 AM UTC

    Compound Actions which have Notify Action in them are failing, we have identified the root cause and have fixed the issue.

Read the full incident report →

Major December 15, 2025

Issues accessing Roles & Permissions Management

Detected by Pingoru
Dec 15, 2025, 05:23 PM UTC
Resolved
Dec 15, 2025, 06:10 PM UTC
Duration
46m
Affected: Moveworks Setup
Timeline · 3 updates
  1. investigating Dec 15, 2025, 05:23 PM UTC

    We are investigating an issue preventing the Roles and Permissions section from loading correctly. Currently, administrative users are unable to view or modify user access settings. Our engineering team is actively looking into the root cause. Impacted Regions: US, EU, CA, AU

  2. investigating Dec 15, 2025, 06:10 PM UTC

    The issue affecting the Roles and Permissions section has been resolved. The service is now fully operational and functioning as expected.

  3. resolved Dec 15, 2025, 06:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 22, 2025

Live Agent Message Brokering Degradation After ServiceNow Zurich upgrade

Detected by Pingoru
Nov 22, 2025, 02:48 AM UTC
Resolved
May 12, 2026, 08:41 PM UTC
Duration
171d 17h
Affected: Live Agent Message Brokering
Timeline · 6 updates
  1. identified Nov 09, 2025, 11:38 PM UTC

    We have identified an issue affecting Live Agent Message Brokering functionality following the ServiceNow Zurich upgrade. Users can initiate chats, and agents can respond, but user replies are not being received by agents. The issue currently impacts customers who have upgraded to Zurich. Our team is working with ServiceNow to identify the root cause and implement a fix. Updates will be shared as they become available. Impacted Regions: All

  2. identified Nov 13, 2025, 04:20 PM UTC

    The ServiceNow team has identified the root cause of the issue affecting live chat functionality. They are actively working on a fix and will provide more details as soon as they become available.

  3. monitoring Nov 22, 2025, 02:48 AM UTC

    ServiceNow has resolved the issue. A hotfix (ZP2 HF2) has been released. If you are impacted, please submit your entitlements using the link below to request access to the hotfix: https://support.servicenow.com/nav_to.do?uri=%2Fcom.glideapp.servicecatalog_cat_item_view.do%3Fsysparm_id%3De9c285831ba414101c8633f2cd4bcbfe

  4. monitoring Dec 02, 2025, 10:36 PM UTC

    We have received confirmation that the same fix has been rolled into Zurich Patch 4(ZP4) which is scheduled to go live on December 5. Once ZP4 becomes available, feel free to upgrade to get the issue resolved.

  5. monitoring Feb 23, 2026, 07:34 AM UTC

    We have noticed that this issue is also impacting the instances which are on Yokohama Patch 9, the fix for the same has been released in the Patch 10. Please refer to the below KB article from ServiceNow for more information. https://support.servicenow.com/nav_to.do?uri=%2Fkb%3Fid%3Dkb_article_view%26sysparm_article%3DKB2683059

  6. resolved May 12, 2026, 08:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 18, 2025

AI Assistant Unresponsive in Microsoft Teams

Detected by Pingoru
Nov 18, 2025, 03:04 PM UTC
Resolved
Nov 18, 2025, 05:58 PM UTC
Duration
2h 54m
Affected: Microsoft Teams
Timeline · 3 updates
  1. investigating Nov 18, 2025, 03:04 PM UTC

    We are currently investigating an issue where the AI Assistant within Microsoft Teams is not responding to users. Our engineering team is actively working to identify and resolve the root cause. We apologize for the inconvenience and appreciate your patience as we restore full service.

  2. monitoring Nov 18, 2025, 03:44 PM UTC

    we’re now seeing improvements and confirm that the AI Assistant in Microsoft Teams is responding to users again. Our team continues to monitor the situation to ensure full stability and will provide further updates if necessary. Thank you for your patience.

  3. resolved Nov 18, 2025, 05:58 PM UTC

    We’re pleased to inform you that the issue affecting interactions with AI Assistant in Microsoft Teams has now been resolved. According to Microsoft, the problem resulted from an unexpected spike in user traffic, which temporarily reduced availability of the service infrastructure. The advisory (reference TM1187642) is now marked as “Service Restored.” For further details or to track any future notices, feel free to follow the Microsoft service health advisory directly via the Microsoft 365 admin center. We apologize for any inconvenience this may have caused and thank you for your patience and understanding during this period.

Read the full incident report →

Minor November 10, 2025

Forms Ingestion Failure

Detected by Pingoru
Nov 10, 2025, 03:54 PM UTC
Resolved
Nov 11, 2025, 07:27 PM UTC
Duration
1d 3h
Affected: Smart Forms
Timeline · 3 updates
  1. identified Nov 10, 2025, 03:54 PM UTC

    We’ve identified an issue in our forms ingestion process. As a result, forms that are newly added or updated after 11/6 may not be appearing in the AI Assistant as expected. Our engineering team is actively working to resolve this issue. We will provide updates as soon as we have more information. We sincerely apologize for the inconvenience this may cause and thank you for your patience.

  2. identified Nov 10, 2025, 04:55 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Nov 11, 2025, 07:27 PM UTC

    This incident has been resolved. Thank you for your patience and we apologize for the inconvenience this may have caused.

Read the full incident report →

Minor November 5, 2025

Live Agent Message Brokering Degradation

Detected by Pingoru
Nov 05, 2025, 03:57 PM UTC
Resolved
Nov 05, 2025, 10:18 PM UTC
Duration
6h 20m
Affected: Live Agent Message BrokeringEmbedded AI Assistant
Timeline · 4 updates
  1. investigating Nov 05, 2025, 03:57 PM UTC

    We’re currently investigating an issue affecting our AI Assistants’ live agent message brokering feature. At this time, the issue appears to be isolated to live agent chats initiated through the Embedded AI Assistant. We’ll provide updates as soon as we have more information. Thank you for your patience.

  2. identified Nov 05, 2025, 04:35 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Nov 05, 2025, 08:11 PM UTC

    A fix has been implemented: we rolled back the changes that caused the issue and the service is now returning to normal. We are actively monitoring to ensure stability. Thanks again for your patience.

  4. resolved Nov 05, 2025, 10:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 3, 2025

Access Redirect Issue at My Moveworks Portal

Detected by Pingoru
Nov 03, 2025, 05:16 PM UTC
Resolved
Nov 03, 2025, 06:34 PM UTC
Duration
1h 17m
Affected: Moveworks SetupMoveworks DocumentationSupportCommunity
Timeline · 3 updates
  1. investigating Nov 03, 2025, 05:16 PM UTC

    We’re currently experiencing an issue that is affecting My Moveworks Portal access for some users. When attempting to reach {mycompany}.moveworks.com, you may be automatically redirected to {mycompany}.moveworks.com/assistant. What we’re doing: Our team is actively investigating and working to resolve this issue as quickly as possible. In the meantime: Please use the alternate URL to access the portal: {mycompany}.moveworks.com/manage We apologize for the inconvenience and appreciate your patience. We will provide an update as soon as we have more information.

  2. monitoring Nov 03, 2025, 05:54 PM UTC

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

  3. resolved Nov 03, 2025, 06:34 PM UTC

    This incident has been resolved.

Read the full incident report →