Walkme Outage History
Walkme is up right nowPingoru has recorded 35 incidents for Walkme: 3 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 314 of 720 (44%) |
| May 2026 | 0 | 22 of 744 (3%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 1 | 50 of 744 (7%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 517 (0%) |
Incidents, newest first
Minor July 10, 2026 Extension not loading on cloud.microsoft domains after an update to the Microsoft Edge Browser (version 150) 2d 1h Browser Extensions
Started Jul 10, 2026, 05:42 PM UTC· resolved Jul 12, 2026, 07:15 PM UTC
- investigating Jul 10, 2026, 05:42 PM UTC
We are currently investigating this issue.
- investigating Jul 10, 2026, 06:56 PM UTC
This is due to an update by MS and impacting multiple extensions. We have escalated to Microsoft and are pushing for a solution as soon as possible.
- investigating Jul 10, 2026, 07:13 PM UTC
We are continuing to investigate this issue.
- investigating Jul 10, 2026, 07:25 PM UTC
We are continuing to investigate this issue.
- resolved Jul 12, 2026, 07:15 PM UTC
Per https://github.com/microsoft/MicrosoftEdge-Extensions/issues/644#issuecomment-4933908795 "Currently, extensions are not designed to work with Copilot. At this time, the list of sites where Microsoft extensions are blocked includes Copilot, Edge:// pages, and EAS*" From our research, it seems that the affected domains are only the following 2 domains: https://m365.cloud.microsoft/ https://copilot.com/
Minor April 17, 2026 Known Chromium Bug Impacting Browser Load Time on Initial Boot Up With the WalkMe Extension Installed on Windows OS 149d 22h
Started Apr 17, 2026, 09:46 PM UTC· resolved Sep 14, 2026, 08:41 PM UTC
- monitoring Apr 17, 2026, 09:46 PM UTC
We have become aware of a known Chromium bug that is intermittently impacting the load time of Edge/Chrome on initial boot up. This behavior is intermittently impacting certain Windows OS users with the WalkMe Extension installed. The Chromium bug is related to Chrome's Service Worker lifecycle, causing network requests or the extension itself to stall and hang indefinitely. The Chromium team is working on resolving the behavior and the progress can be followed by visiting the following link: https://issues.chromium.org/issues/484218883 If you believe you may be impacted, please open a case to the WalkMe Support team who will be able to assist with applying an interim solution while the bug is being patched.
- resolved Sep 14, 2026, 08:41 PM UTC
This incident has been resolved.
Notice November 3, 2025 WalkMe content is not appearing for multiple customers. –
Started Nov 03, 2025, 03:00 PM UTC· resolved Nov 03, 2025, 03:00 PM UTC
- resolved Nov 03, 2025, 04:34 PM UTC
WalkMe content is not appearing for multiple customers due to DeepUI being down. Resolved by 16:26 UTC
Major June 12, 2025 Insights Reporting Outage 1d Insights reports
Started Jun 12, 2025, 07:33 PM UTC· resolved Jun 13, 2025, 08:26 PM UTC
- investigating Jun 12, 2025, 07:33 PM UTC
We are currently investigating this issue.
- monitoring Jun 12, 2025, 07:36 PM UTC
We are seeing that the issue is stabilizing and we are currently monitoring the results.
- monitoring Jun 12, 2025, 07:36 PM UTC
We are continuing to monitor for any further issues.
- resolved Jun 13, 2025, 08:26 PM UTC
This incident has been resolved.
Major June 2, 2025 WalkMe intermittently loading with a delay 4h 39m Web Player
Started Jun 02, 2025, 03:50 PM UTC· resolved Jun 02, 2025, 08:30 PM UTC
- investigating Jun 02, 2025, 03:50 PM UTC
We have received reports of WalkMe intermittently loading with a slight delay for some customers
- identified Jun 02, 2025, 07:05 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 02, 2025, 07:10 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 03, 2025, 01:08 PM UTC
This incident has been resolved.
Minor March 21, 2025 Temporary disruption in publish capability on US datacenter –
Started Mar 21, 2025, 11:30 PM UTC· resolved Mar 21, 2025, 11:30 PM UTC
- resolved Mar 27, 2025, 07:55 PM UTC
Unable to publish content or settings on any US account. Error will display in Editor "Update and Publish error" The incident affected 40 systems that attempted to publish during the timeframe.
Major October 22, 2024 Microsoft Edge Bug Impacting Extensions 2d 22h
Started Oct 22, 2024, 04:53 PM UTC· resolved Oct 25, 2024, 02:59 PM UTC
- identified Oct 22, 2024, 04:53 PM UTC
Due to a bug introduced in the newest Microsoft Edge version, many browser extensions, including the WalkMe extension, may fail to work properly on Edge versions 130 or later. Microsoft has confirmed they are working to revert the impacted Edge versions in the next release, which is scheduled for this week. An update will be provided once a more detailed release schedule is provided. WalkMe engineering has been able to determine the following workarounds to review with your IT team for an immediate solution as an alternative to waiting for the Microsoft fix. Unique Extension Deployment: WalkMe can provide a new extension that can be mass-deployed by your IT team. Please reach out to WalkMe Support for assistance. The unique extension offers additional long term benefits including: Quicker access to extension hotfixes and new features than the Edge webstore Enhanced security controls - URL allow and block lists to control where WalkMe is allowed to play Branding customizations - Customize the name and description end users see in the browser Ability to disable auto updates and control updates Reverting Edge Version: Revert to a previous version of Microsoft Edge, specifically version 128. Please find a link to the Microsoft bug here: https://github.com/microsoft/MicrosoftEdge-Extensions/issues/179
- identified Oct 23, 2024, 06:25 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 24, 2024, 11:13 PM UTC
Microsoft has released a fix for this issue in Edge stable version 130.0.2849.56. Please see their status page update under version 130 here: https://learn.microsoft.com/en-us/deployedge/microsoft-edge-known-issues#high-impact-issues With this Microsoft fix for the Edge store extension, the workaround WalkMe offered in regard to a unique extension is no longer needed. However, we'd like to highlight the benefits below if this is something users would like to convert to in the long-term. Please feel free to reach out to WalkMe Support for any assistance. Quicker access to extension hotfixes and new features than the Edge webstore Enhanced security controls - URL allow and block lists to control where WalkMe is allowed to play Branding customizations - Customize the name and description end users see in the browser Ability to disable auto updates and control updates
- resolved Oct 25, 2024, 02:59 PM UTC
Microsoft has released a fix for this issue in Edge stable version 130.0.2849.56. Please see their status page update under version 130 here: https://learn.microsoft.com/en-us/deployedge/microsoft-edge-known-issues#high-impact-issues With this Microsoft fix for the Edge store extension, the workaround WalkMe offered in regard to a unique extension is no longer needed - however, we'd like to highlight the benefits of switching to a unique extension, in order for you to make an informed decision as to if this is something you would like to convert to in the future. Those benefits include: Quicker access to extension hotfixes and new features than the Edge webstore Enhanced security controls - URL allow and block lists to control where WalkMe is allowed to play Branding customizations - Customize the name and description end users see in the browser Ability to disable auto updates and control updates