Walkme status history
Current state: operational — “All Systems Operational” per https://status.walkme.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Walkme incidents last?
From 3 incidents with a vendor-posted start and resolve time. Longest on record: Known Chromium Bug Impacting Browser Load Time on Initial Boot Up With the WalkMe Extension Installed on Windows OS — 150.0 days (2026-04-17 21:46 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (3)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-10 17:42 UTC | Extension not loading on cloud.microsoft domains after an update to the Microsoft Edge Browser (version 150) | resolved | minor | 2 d 1 h |
| 2026-04-17 21:46 UTC | Known Chromium Bug Impacting Browser Load Time on Initial Boot Up With the WalkMe Extension Installed on Windows OS | resolved | minor | 149 d 22 h |
| 2025-11-03 15:00 UTC | WalkMe content is not appearing for multiple customers. | resolved | none | 0 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Walkme with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"walkme"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
