Workspot status history
Current state: operational — “All Systems Operational” per https://status.workspot.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Workspot incidents last?
From 9 incidents with a vendor-posted start and resolve time. Longest on record: Users are experiencing Authentication failures while using Workspot Windows Client. — 15.5 days (2025-10-15 18:58 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 (9)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-05-21 16:05 UTC | Azure East US Capacity Constraints Impacting Virtual Desktop Availability | resolved | none | 11 d 5 h |
| 2026-05-05 12:08 UTC | Intermittent Restarts of Control Dynos | resolved | none | 16 h 24 min |
| 2026-04-24 13:31 UTC | VM Connectivity Issues – Azure East US | resolved | minor | 3 d 17 h |
| 2026-03-20 18:09 UTC | Workspot Control Reported Five Minutes Downtime | resolved | none | 3 d 11 h |
| 2026-02-02 09:38 UTC | Workspot Control Experiencing Intermittent Availability | resolved | none | 41 h 50 min |
| 2025-11-14 15:57 UTC | Workspot Control Login Instability | resolved | major | 2 h 33 min |
| 2025-10-20 17:11 UTC | AWS Operational Issues - No Impact - Workspot is closely monitoring the situation | resolved | none | 10 d 13 h |
| 2025-10-15 18:58 UTC | Users are experiencing Authentication failures while using Workspot Windows Client. | resolved | none | 15 d 11 h |
| 2025-09-10 14:43 UTC | Failure in Azure East US and East US2 region | resolved | none | 6 d 13 h |
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 Workspot with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"workspot"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}