Jul <var data-var='date'> 7</var>, <var data-var='time'>06:30</var> UTC Completed - The scheduled maintenance has been completed. Jul <var data-var='date'> 7</var>, <var data-var='time'>05:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>26</var>, <var data-var='time'>07:59</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators will not be able to log in to Control, and end users will not be able to launch new non-persistent desktop sessions. Existing end-user sessions will not be impacted, and end users can launch persistent desktops.

Workspot EU Control Upgrade to R26.6 on July 7th at 0530 UTC

Jul <var data-var='date'> 3</var>, <var data-var='time'>03:00</var> UTC Completed - The scheduled maintenance has been completed. Jul <var data-var='date'> 3</var>, <var data-var='time'>02:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>26</var>, <var data-var='time'>07:58</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators will not be able to log in to Control, and end users will not be able to launch new non-persistent desktop sessions. Existing end-user sessions will not be impacted, and end users can launch persistent desktops.

Workspot US Control Upgrade to R26.6 on July 3rd at 0200 UTC

Jun <var data-var='date'>30</var>, <var data-var='time'>04:30</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>30</var>, <var data-var='time'>03:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'> 1</var>, <var data-var='time'>16:00</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, Trends users cannot log in to Workspot Trends. All other services, Control, Watch, and end-user sessions will not be impacted. To know more about Workspot Trends, Please refer: https://docs.workspot.com/docs/using-workspot-trends

Workspot US Trends Upgrade to R2.8.0 on June 30th at 03:30 AM UTC

Jun <var data-var='date'>27</var>, <var data-var='time'>04:30</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>27</var>, <var data-var='time'>03:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'> 1</var>, <var data-var='time'>16:03</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, Trends users cannot log in to Workspot Trends. All other services, Control, Watch, and end-user sessions will not be impacted. To know more about Workspot Trends, Please refer: https://docs.workspot.com/docs/using-workspot-trends

Workspot EU Trends Upgrade to R2.8.0 on June 27th  at 03:30 AM UTC

Jun <var data-var='date'>23</var>, <var data-var='time'>04:00</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>23</var>, <var data-var='time'>03:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'> 1</var>, <var data-var='time'>16:07</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators cannot log in to Workspot Watch. All other services, Control, Trends, and end-user sessions will not be impacted. To know more about Workspot Watch release updates, Please refer: https://docs.workspot.com/docs/using-workspot-watch

Workspot EU Watch Upgrade to R6.7.0 on June 23rd, at 03:30 AM UTC

Jun <var data-var='date'>20</var>, <var data-var='time'>04:00</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>20</var>, <var data-var='time'>03:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'> 1</var>, <var data-var='time'>16:05</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators cannot log in to Workspot Watch. All other services, Control, Trends, and end-user sessions will not be impacted. To know more about Workspot Watch release updates, Please refer: https://docs.workspot.com/docs/using-workspot-watch

Workspot US Watch Upgrade to R6.7.0 on June 20th, at 03:30 AM UTC

Jun <var data-var='date'> 9</var>, <var data-var='time'>06:30</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'> 9</var>, <var data-var='time'>05:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'>18</var>, <var data-var='time'>05:47</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators will not be able to log in to Control, and end users will not be able to launch new non-persistent desktop sessions. Existing end-user sessions will not be impacted, and end users can launch persistent desktops.

Workspot EU Control Upgrade to R26.5 on June 09th at 0530 UTC

Jun <var data-var='date'> 6</var>, <var data-var='time'>03:00</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'> 6</var>, <var data-var='time'>02:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'> 1</var>, <var data-var='time'>16:12</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators will not be able to log in to Control, and end users will not be able to launch new non-persistent desktop sessions. Existing end-user sessions will not be impacted, and end users can launch persistent desktops.

Workspot US Control Upgrade to R26.5 on June 6th at 2:00 AM UTC

Jun <var data-var='date'> 1</var>, <var data-var='time'>21:47</var> UTC Resolved - Update from Microsoft: Current Status: Resolved What went wrong and why? Due to an increase in demand for compute resources in a particular zone in the region, there were capacity constraints on available compute infrastructure. This in turn resulted in service management operation and allocation failures for VM resources. How did we respond? We’ve load balanced the capacity demands and restored the capacity buffers to a healthy state. With the congestion resolved, services should now function as usual. What happens next? •	Ensuring capacity for our customers is a top priority for Microsoft. We sincerely apologize for any impact this may have caused, but be assured, we are continuously improving tools around monitoring usage, forecasting stock out, maintaining healthy buffers and improving cycle times to reduce this type of issue from happening. May <var data-var='date'>22</var>, <var data-var='time'>12:45</var> UTC Update - Update from Microsoft: Current Status: Due to an increase in demand for compute resources in the region, there are capacity constraints on available compute infrastructure. This in turn resulted in service management operation and allocation failures for VM resources. We are currently working on platform levers to restore healthy buffers in relation to capacity. We will continue to monitor the situation and supply updates accordingly. An update will be provided on 28 May 2026, or as events warrant. May <var data-var='date'>21</var>, <var data-var='time'>16:05</var> UTC Identified - Dear Customer, Workspot has identified an issue affecting the availability of Virtual Desktops hosted in the Azure East US region. Microsoft has confirmed ongoing Azure Compute capacity constraints in this region. Customers attempting to create, update, resume, scale, start, or restart Virtual Machines may experience allocation failures. Current Impact: - VM lifecycle operations may intermittently fail - Running desktops are not impacted unless restarted or redeployed How to Check if You Are Impacted: If your subscription is affected, details will be visible under: -->Azure Portal → Service Health → Active / Maintenance Events Workaround: - Redeploy the Virtual Machine from Workspot Control to help bring it online Recommendations: - Try a different Availability Zone within East US - Use an alternate Azure region with lower demand Mitigation Options: - Disable Pause/Resume (VM runs continuously; may increase cost) - On-demand Capacity Reservation: https://learn.microsoft.com/azure/virtual-machines/capacity-reservation-overview - Reserved Instances (cost benefit + prioritized capacity): https://learn.microsoft.com/azure/cost-management-billing/reservations/save-compute-costs-reservations Ongoing Actions: Workspot is actively engaged with Microsoft and monitoring the situation closely.

Azure East US Capacity Constraints Impacting Virtual Desktop Availability

May <var data-var='date'>12</var>, <var data-var='time'>04:00</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'>12</var>, <var data-var='time'>03:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>28</var>, <var data-var='time'>17:13</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators cannot log in to Workspot Watch. All other services, Control, Trends, and end-user sessions will not be impacted. To know more about Workspot Watch release updates, Please refer: https://docs.workspot.com/docs/using-workspot-watch

Workspot EU Watch Upgrade to R6.6.0 on May 12th, at 03:30 AM UTC

May <var data-var='date'> 9</var>, <var data-var='time'>04:00</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'> 9</var>, <var data-var='time'>03:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>28</var>, <var data-var='time'>17:10</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators cannot log in to Workspot Watch. All other services, Control, Trends, and end-user sessions will not be impacted. To know more about Workspot Watch release updates, Please refer: https://docs.workspot.com/docs/using-workspot-watch

Workspot US Watch Upgrade to R6.6.0 on May 09, at 03:30 AM UTC

May <var data-var='date'> 6</var>, <var data-var='time'>04:32</var> UTC Resolved - Workspot investigated the restart of the Control Dynos reported by our platform provider. The system is stable and we are closing the incident on status, but continuing to actively monitor and investigate the root cause. We will share the RCA and updates as soon as they become available. Thank you. May <var data-var='date'> 5</var>, <var data-var='time'>19:01</var> UTC Update - There are no new updates at this time. The platform remains stable, and the engineering team continues to monitor the environment. If there are no changes, the next update will be shared in the next 2 hours. We will provide further updates sooner if needed. May <var data-var='date'> 5</var>, <var data-var='time'>16:33</var> UTC Update - No new update at this time. The platform remains stable, and the engineering team continues to actively monitor the environment. If there are no changes, the next update will be shared in the next two hours. We will provide an update sooner if there is any change in status. May <var data-var='date'> 5</var>, <var data-var='time'>14:33</var> UTC Update - There are no new updates at this time. The platform remains stable, and the engineering team continues to monitor the environment. If there are no changes, the next update will be shared in the next 2 hours. We will provide further updates sooner if needed. May <var data-var='date'> 5</var>, <var data-var='time'>13:37</var> UTC Update - No new issues have been observed. As a mitigation measure, the engineering team has implemented changes to improve platform stability. The team is closely monitoring the environment and continues to investigate the underlying cause of the earlier instability. The next update will be shared in one hour. We will provide further updates sooner if there are any changes. May <var data-var='date'> 5</var>, <var data-var='time'>13:06</var> UTC Update - We have not observed any dyno restarts since the incident was reported, nor any application downtime. The engineering team continues to monitor the environment closely and is investigating the underlying cause of the earlier dyno restarts. We will provide further updates as more information becomes available. May <var data-var='date'> 5</var>, <var data-var='time'>12:35</var> UTC Update - We have not observed any dyno restarts in the last 30 minutes. The engineering team is closely monitoring the environment and continues to investigate the underlying cause of the earlier dyno restarts. We will provide further updates as more information becomes available. May <var data-var='date'> 5</var>, <var data-var='time'>12:08</var> UTC Investigating - We are observing intermittent dynos restarts reported by our platform provider, Heroku. At this time, we have not observed any application downtime. This activity is not related to any security incident. Our engineering team is actively investigating the issue. We will continue to provide updates as we learn more.

Intermittent Restarts of Control Dynos

Apr <var data-var='date'>28</var>, <var data-var='time'>06:52</var> UTC Resolved - Update: We have received the Preliminary Post Incident Review(PIR) from Microsoft for the Azure East US control plane issue that impacted your environment on April 24. Here is a summary of what happened and why: STATUS: RCA COMMUNICATION: This is our Preliminary PIR to share what we know so far. After our internal retrospective is completed (generally within 14 days) we will publish a Final PIR with additional details. What happened? Between 11:30 UTC on 24 April and 00:15 UTC on 25 April 2026, customers may have experienced failures or delays when attempting to provision, scale, or update resources in East US. Beyond this, a smaller subset of impacted customers may have experienced intermittent connectivity issues on existing workloads (including Virtual Machines and Azure Virtual Desktop sessions) for scenarios dependent on unhealthy internal service dependencies. The issue initially began with impact to a subset of customers in a single Availability Zone (physical AZ-01) but as demand shifted, similar symptoms were observed impacting a subset of customers in AZ-02 and AZ-03. While none of these zones were impacted for the full duration of the incident, customers experienced periods of impact in each zone for portions of the incident. The following services were among those affected: Azure Application Gateway, Azure App Service, Azure Batch, Azure Cache for Redis, Azure Data Explorer, Azure Data Factory, Azure Databricks, Azure Health Data Services, Azure Kubernetes Service (AKS), Azure Red Hat OpenShift, Azure Service Fabric, Azure Synapse Analytics, Azure Virtual Desktop, Azure Virtual Machines, Azure Virtual Network Manager, Azure VMware Solution, Oracle Database@Azure, Virtual Machine Scale Sets – and potentially additional services that were dependent on new compute allocations in the region. Note: Logical availability zones assigned to customer subscriptions may map to different physical availability zones. Customers can use the Locations API to understand this mapping: https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations?HTTP#availabilityzonemappings. What went wrong and why? The Azure PubSub service is a key component of the networking control plane, acting as an intermediary between resource providers and networking agents on Azure hosts. Resource providers, such as the Network Resource Provider, publish customer configurations during Virtual Machine or networking create, update, or delete operations. Networking agents (subscribers) on the hosts retrieve these configurations to program the hosts networking stack. Additionally, the service functions as a cache, ensuring efficient retrieval of configurations during VM reboots or restarts. This capability is essential for deployments, resource allocation, and traffic management in Azure Virtual Network (VNet) environments. During normal platform operations, one partition of this PubSub service in AZ-01 became unhealthy and automatically attempted to fail over to a secondary replica. The failover did not complete successfully, resulting in a partial loss of control plane availability within AZ-01. We intervened to investigate and attempted a manual failover of the primary partition, but this attempt was also unsuccessful. Shortly afterward, we observed a similar condition in AZ-03, which led to a partial loss of control plane availability in AZ-03 as well. As the investigation progressed, we suspected that a previously deployed update to a regional control plane dependency had introduced a latent regression. This issue did not surface during earlier validation and only manifested when failover conditions were triggered under sustained production load. As part of our mitigation efforts, we identified a version from the prior week that represented a Last Known Good (LKG) state. We first applied this rollback in AZ-03, which successfully restored control plane service health in that zone. Based on this, we began rolling back the affected components in AZ-01. By design, rollback operations are executed in stages by Azure Fabric controllers using update domains to ensure platform safety, while recovery proceeds incrementally. While mitigation was in progress, the platform was unable to maintain two healthy instances of the PubSub service across availability zones simultaneously, which is a requirement for normal replication and control plane operations. This resulted in a loss of quorum of the service. As the system attempted to rebalance, impact shifted between availability zones, leading to periods of degraded behavior across multiple zones. Similar failure patterns began to appear in AZ-02 and again in AZ-03, expanding the scope of impact across the region. For AZ-02 we initiated and completed a rollback, and although AZ-03 had previously shown recovery following the rollback, subsequent instability indicated that the rollback in that zone had not fully completed, because of an orchestration fault. As impact reemerged, rollback operations in AZ-03 were restarted and then completed, fully restoring service health. How did we respond? •	11:30 UTC on 24 April 2026 – Customer impact began. We observed failures or delays when customers attempted to provision, scale, or update resources in the affected region. •	11:38 UTC on 24 April 2026 – We detected an issue in AZ-01. A control plane partition became unhealthy and automatic failover attempts did not complete successfully. •	11:38–13:40 UTC on 24 April 2026 – We attempted manual failover in AZ-01. These efforts did not successfully restore service. •	13:40 UTC on 24 April 2026 – We identified a recently deployed update as the likely cause of the issue. •	13:50 UTC on 24 April 2026 – We began observing similar symptoms in AZ-03, indicating the issue was affecting multiple availability zones. •	14:07 UTC on 24 April 2026 – We initiated rollback to a previously known good version in AZ-03. •	15:03 UTC on 24 April 2026 – We observed significant recovery in AZ-03. Control plane availability exceeded 99%. •	15:04 UTC on 24 April 2026 – We initiated rollback actions to AZ-01. •	18:52 UTC on 24 April 2026 – We observed significant improvement in AZ-01 as rollback progressed. •	19:02 UTC on 24 April 2026 – We confirmed AZ-01 had recovered to greater than 99% availability, while the rollback continued in the background. •	19:05 UTC on 24 April 2026 – We observed similar symptoms in AZ-02 as load redistributed across the region. •	19:10 UTC on 24 April 2026 – We initiated rollback to a known good version in AZ-02. •	21:02 UTC on 24 April 2026 – We observed instability reappear in AZ-03. We determined this was because the rollback had not yet completed across all update domains. Consequently, we manually unblocked the rollback across remaining update domains in AZ03 to ensure stable recovery. •	22:39 UTC on 24 April 2026 – We confirmed rollback was fully completed in AZ-03. •	23:22 UTC on 24 April 2026 – We confirmed rollback was fully completed in AZ-02, completing PubSub mitigation across all affected zones. •	00:15 UTC on 25 April 2026 – We validated downstream service recovery and PubSub health across all zones in the region. How are we making incidents like this less likely or less impactful? •	We have assessed the risk of occurrence in other high volume regions, and have taken steps to rollback this PubSub service in these regions out of an abundance of caution. (Completed) •	We are investing in improving our test coverage surrounding the failure cases and load patterns that contributed to this incident, to catch issues like this one before they reach production. (Estimated completion: TBD) •	We are working to reduce rollback complexity, to be able to mitigate issues like this more quickly in future. (Estimated completion: TBD) •	This is our Preliminary PIR to share what we know so far. After our internal retrospective is completed (generally within 14 days) we will publish a Final PIR with additional details. How can customers make incidents like this less impactful? •	Consider using Availability Zones (AZs) to run your services across physically separate locations within an Azure region. To help services be more resilient to localized failures like this one (which predominantly impacted zones at different times) many Azure services support zonal, zone-redundant, and/or always-available configurations: https://docs.microsoft.com/azure/availability-zones/az-overview •	For mission-critical workloads, customers should consider a multi-region geodiversity strategy to avoid impact from incidents like this one that impacted a single region: https://learn.microsoft.com/azure/architecture/patterns/geodes and https://learn.microsoft.com/azure/well-architected/design-guides/regions-availability-zones •	More generally, consider evaluating the reliability of your applications using guidance from the Azure Well-Architected Framework and its interactive Well-Architected Review: https://aka.ms/AzPIR/WAF •	The impact times above represent the full incident duration, so are not specific to any individual customer. Actual impact to service availability varied between customers and resources – for guidance on implementing monitoring to understand granular impact: https://aka.ms/AzPIR/Monitoring •	Finally, consider ensuring that the right people in your organization will be notified about any future service issues – by configuring Azure Service Health alerts. These can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/AzPIR/Alerts Apr <var data-var='date'>25</var>, <var data-var='time'>04:15</var> UTC Monitoring - Update: Microsoft has shared below update on the ongoing Azure platform incident impacting Virtual Machines and Virtual Machine Scale Sets in the East US region. Current Status: Resolved What happened? Between 11:39 UTC on 24th April and 00:15 UTC on 25 April 2026, a platform issue resulted in an impact to a subset of Azure services in the East US region. Impacted customers experienced failures or delays when provisioning, scaling, or updating Azure resources. Intermittent connectivity issues may also be seen on existing running workloads in Virtual Machines and Azure Virtual Desktop sessions. This issue is now mitigated. An update with more information will be provided shortly. Next Steps: The next update will be shared once Microsoft provides the RCA. In the meantime, Workspot will continue to monitor impacted pools and virtual desktops to ensure stability and identify any residual issues. Apr <var data-var='date'>24</var>, <var data-var='time'>23:38</var> UTC Update - Microsoft has shared below update on the ongoing Azure platform incident impacting Virtual Machines and Virtual Machine Scale Sets in the East US region. Current Status: Rollback is complete for Availability Zone (AZ) 01 and AZ03, and is still in progress for AZ02. Mitigation is expected to complete within the next 1 hour. Customers should observe improvements to their services, and downstream services are also starting to recover. NEXT STEPS: The next update will be shared within 60 minutes, or as events warrant. Apr <var data-var='date'>24</var>, <var data-var='time'>17:56</var> UTC Update - Microsoft has shared below update on the ongoing Azure platform incident impacting Virtual Machines and Virtual Machine Scale Sets in the East US region. CURRENT STATUS: We detected this issue through automated monitoring after identifying an unusual drop in service success rates. The issue was caused by a recent change, and rollback actions are in progress across availability zones (AZs). Customers may begin to see recovery if using resources in AZ03, with Availability Zone 01 currently in progress. Please refer to this documentation to understand the logical to physical availability zone mapping for your subscription. However, there is no confirmed estimated time for full resolution at this moment. The next update will be shared within the next 60 minutes, or as events warrant. Apr <var data-var='date'>24</var>, <var data-var='time'>17:06</var> UTC Update - Current Status: At this time, no new update has been received from Microsoft beyond their previous communication. The incident remains under investigation on their side. We are continuing to monitor the situation closely and are tracking customer impact, which currently includes multiple reported cases of virtual desktop connectivity issues and VM accessibility failures. Next Update: We will provide an update as soon as Microsoft shares further information or once there is any material change in status. Apr <var data-var='date'>24</var>, <var data-var='time'>15:52</var> UTC Update - Microsoft has shared an update on the ongoing Azure platform incident impacting Virtual Machines and Virtual Machine Scale Sets in the East US region. Microsoft identified the issue through automated monitoring, which detected an unusual increase in failures within the service supporting virtual machine operations in East US. Microsoft is currently investigating the underlying cause and is actively working toward mitigation. Current Status: The issue remains in progress and under investigation by Microsoft. Customers may continue to experience VM connectivity or access issues in East US, and related impact may also be seen in East Asia. Microsoft indicated that the next update will be shared within approximately 60 minutes, or sooner if there are meaningful developments. Workspot continues to monitor the situation closely and will provide further updates as new information becomes available from Microsoft. Apr <var data-var='date'>24</var>, <var data-var='time'>14:38</var> UTC Update - Update from the Microsoft: Service: Virtual Machine Scale Sets, Virtual Machines Region: East US, East Asia Impact Statement: Starting at 11:39 UTC on 24 Apr 2026, a subset of customers using Virtual Machines and Virtual Machine Scale Sets in East US may experience issues with resources hosted in this region. Current Status:  We are aware of this issue and are actively investigating. The next update will be provided as events warrant. IMPACTED SERVICE(S) AND REGION(S): Service Name 	Region Virtual Machine Scale Sets -->East US Virtual Machines	--> East Asia Apr <var data-var='date'>24</var>, <var data-var='time'>13:38</var> UTC Update - Impact Statement: Starting at 11:39 UTC on 24 Apr 2026, a subset of customers using Virtual Machines and Virtual Machine Scale Sets in East US may experience issues with resources hosted in this region. Current Status: We are aware of this issue and are actively investigating. The next update will be provided as events warrant. IMPACTED SERVICE(S) AND REGION(S): Service Name 	Region Virtual Machine Scale Sets -->East US Virtual Machines	--> East Asia Apr <var data-var='date'>24</var>, <var data-var='time'>13:31</var> UTC Investigating - Workspot has identified an issue affecting accessibility of virtual desktops hosted in the Azure East US region. Microsoft has confirmed an ongoing Azure platform incident impacting a subset of Virtual Machines and Virtual Machine Scale Sets in this region. As a result, some customers may experience loss of network connectivity or inability to access their VMs. This Azure incident aligns with the connectivity issues currently being observed. Workspot is monitoring the situation closely and is in communication with Microsoft regarding the incident status. We will provide updates as they become available.

VM Connectivity Issues – Azure East US

Apr <var data-var='date'>14</var>, <var data-var='time'>06:30</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'>14</var>, <var data-var='time'>05:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>25</var>, <var data-var='time'>14:08</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators will not be able to log in to Control, and end users will not be able to launch new non-persistent desktop sessions. Existing end-user sessions will not be impacted, and end users can launch persistent desktops.

Workspot EU Control Upgrade to R26.4 on April 14th at 0530 UTC

Apr <var data-var='date'>11</var>, <var data-var='time'>03:00</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'>11</var>, <var data-var='time'>02:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>25</var>, <var data-var='time'>14:06</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators will not be able to log in to Control, and end users will not be able to launch new non-persistent desktop sessions. Existing end-user sessions will not be impacted, and end users can launch persistent desktops.

Workspot US Control Upgrade to R26.4 on April 11th at 0200 UTC

Apr <var data-var='date'> 2</var>, <var data-var='time'>05:30</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'> 2</var>, <var data-var='time'>04:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>26</var>, <var data-var='time'>12:06</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, Trends users cannot log in to Workspot Trends. All other services, Control, Watch, and end-user sessions will not be impacted. To know more about Workspot Trends, Please refer: https://docs.workspot.com/docs/using-workspot-trends

Workspot US Trends Upgrade to R2.7.0 on April 2nd at 0430 UTC

Mar <var data-var='date'>30</var>, <var data-var='time'>04:00</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>30</var>, <var data-var='time'>03:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>26</var>, <var data-var='time'>12:08</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, Trends users cannot log in to Workspot Trends. All other services, Control, Watch, and end-user sessions will not be impacted. To know more about Workspot Trends, Please refer: https://docs.workspot.com/docs/using-workspot-trends

Workspot EU Trends Upgrade to R2.7.0 on March 30th at 0300 UTC

Mar <var data-var='date'>24</var>, <var data-var='time'>05:17</var> UTC Resolved - The system has been stable and functioning normally for the past 48 hours. Our internal investigation found no application-level anomalies. We are closing this incident while the root cause analysis (RCA) from our infrastructure provider is still ongoing. We will share updates as soon as they become available. Thank you for your patience. Mar <var data-var='date'>20</var>, <var data-var='time'>18:09</var> UTC Investigating - Pingdom reported production was down for Five minutes(4:08 PM UTC - 4:13 PM UTC). There was a 5 minute intermittent service outage by a subservice provider resetting their system.  The service automatically recovered.  We will share the RCA once we receive from the subservice provider.

Workspot Control Reported Five Minutes Downtime

Mar <var data-var='date'>14</var>, <var data-var='time'>04:30</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>14</var>, <var data-var='time'>03:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>24</var>, <var data-var='time'>08:52</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators cannot log in to Workspot Watch. All other services, Control, Trends, and end-user sessions will not be impacted. To know more about Workspot Watch release updates, Please refer: https://docs.workspot.com/docs/using-workspot-watch

Workspot US Watch Upgrade to R6.5.0 on March 14th, at 0330 UTC

Mar <var data-var='date'>10</var>, <var data-var='time'>07:00</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>10</var>, <var data-var='time'>06:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>24</var>, <var data-var='time'>08:49</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators cannot log in to Workspot Watch. All other services, Control, Trends, and end-user sessions will not be impacted. To know more about Workspot Watch release updates, Please refer: https://docs.workspot.com/docs/using-workspot-watch

Workspot EU Watch Upgrade to R6.5.0 on March 10th, at 0630 UTC

Mar <var data-var='date'>10</var>, <var data-var='time'>06:30</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>10</var>, <var data-var='time'>05:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>24</var>, <var data-var='time'>08:48</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators will not be able to log in to Control, and end users will not be able to launch new non-persistent desktop sessions. Existing end-user sessions will not be impacted, and end users can launch persistent desktops.

Workspot EU Control Upgrade to R26.2 on March 10th 2026 at 0530 UTC

Mar <var data-var='date'> 7</var>, <var data-var='time'>03:00</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'> 7</var>, <var data-var='time'>02:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>24</var>, <var data-var='time'>08:48</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators will not be able to log in to Control, and end users will not be able to launch new non-persistent desktop sessions. Existing end-user sessions will not be impacted, and end users can launch persistent desktops.

Workspot US Control Upgrade to R26.2 on March 7th 2026 at 0200 UTC

Feb <var data-var='date'> 6</var>, <var data-var='time'>19:04</var> UTC Completed - The maintenance is now complete. All functionality has now returned to normal. Thank you! Feb <var data-var='date'> 6</var>, <var data-var='time'>18:57</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'> 6</var>, <var data-var='time'>18:47</var> UTC Scheduled - Heroku is performing maintenance to their EMEA instance, which may effect customers who are using the Workspot EU Control instance. The maintenance will be performed on 06-Feb-2026 between the hours of: 18:00 UTC until 23:00 UTC. We have received some details about which services will be impacted but unclear if this will impact Workspot EU Control. We have contacted Heroku to clarify what services, if any will be impacted. Workspot is monitoring the availability of the EU instance and will post updates here.

Possible impact to the Workspot EU Control Instance

Feb <var data-var='date'> 4</var>, <var data-var='time'>03:28</var> UTC Resolved - The service has been fully restored after the rollback was performed. We appreciate your patience. A detailed Root Cause Analysis (RCA) will be shared once available. Feb <var data-var='date'> 4</var>, <var data-var='time'>03:22</var> UTC Update - We are continuing to monitor for any further issues. Feb <var data-var='date'> 3</var>, <var data-var='time'>11:00</var> UTC Update - Following the rollback performed, no new issues have been reported. Customers have confirmed that the Workspot service is stable. Workspot Control is operating as expected, and all requests are being handled properly. Feb <var data-var='date'> 2</var>, <var data-var='time'>21:41</var> UTC Monitoring - Engineering team has completed the rollback, and all services have now been successfully restored. We are continuing to monitor the environment and will keep you posted with any further updates. We greatly appreciate your patience and cooperation. Feb <var data-var='date'> 2</var>, <var data-var='time'>20:22</var> UTC Update - Engineering team is estimating 90 minutes to complete rollback testing and then a short maintenance window to rollback at approximately 1030 PM UTC. We will update as timeline firm up. We appreciate your patience as we work to restore service stability. Feb <var data-var='date'> 2</var>, <var data-var='time'>19:56</var> UTC Update - There is no new update at this time. Engineering team has made internal progress reviewing the rollback code, and testing activities are ongoing. We will share another update as soon as more information becomes available. We appreciate your continued patience as we work to restore service stability. Feb <var data-var='date'> 2</var>, <var data-var='time'>19:09</var> UTC Update - Engineering team has made internal progress reviewing the rollback code, and testing activities are ongoing. We will share another update as soon as more information becomes available. We appreciate your continued patience as we work to restore service stability. Feb <var data-var='date'> 2</var>, <var data-var='time'>18:33</var> UTC Update - There is no new update at this time. The Engineering team continues to review the rollback plan and assess next steps. We will share another update as soon as more information becomes available. We appreciate your continued patience as we work to restore service stability. Feb <var data-var='date'> 2</var>, <var data-var='time'>18:04</var> UTC Update - There is no new update at this time. The Engineering team continues to review the rollback plan and assess next steps. We will share another update as soon as more information becomes available. We appreciate your continued patience as we work to restore service stability. Feb <var data-var='date'> 2</var>, <var data-var='time'>17:31</var> UTC Update - There is no new update at this time. The Engineering team continues to review the rollback plan and assess next steps. We will share another update as soon as more information becomes available. We appreciate your continued patience as we work to restore service stability. Feb <var data-var='date'> 2</var>, <var data-var='time'>17:00</var> UTC Update - The Engineering team is continuing to assess the rollback plan and review the code changes. An ETA is being evaluated based on the outcome of the review and associated testing. We appreciate your patience as we work to restore service stability. Feb <var data-var='date'> 2</var>, <var data-var='time'>16:31</var> UTC Update - The Engineering team is planning to roll back the release deployed over the weekend. We will continue to share status updates approximately every 30 minutes. An ETA is currently being assessed, and we will provide further updates as more information becomes available. We appreciate your patience as we work to restore service stability. Feb <var data-var='date'> 2</var>, <var data-var='time'>16:15</var> UTC Update - Control is actively accepting requests; however, responses may be intermittent due to a high volume of queued requests. - Control login: Login requests may occasionally time out. Retrying may be successful. - User login: Most users can establish a session. If an issue occurs, please retry. Our Engineering team is also exploring a potential rollback option while ensuring data consistency. We are working to determine an ETA and will provide an update as soon as more information becomes available. We appreciate your patience as we continue to improve service stability. Feb <var data-var='date'> 2</var>, <var data-var='time'>14:58</var> UTC Update - Our engineering team continues to review the impact areas and complete validation to ensure service stability. There are no new updates since our last communication. Feb <var data-var='date'> 2</var>, <var data-var='time'>12:43</var> UTC Update - Our engineering team is still reviewing the impact areas and completing validation to ensure service stability. We will share more details as they become available. Feb <var data-var='date'> 2</var>, <var data-var='time'>11:12</var> UTC Update - The issue has been identified, and corrective measures are in place. Our engineering team is reviewing remaining impact areas and completing final validation to ensure service stability before rollout. Feb <var data-var='date'> 2</var>, <var data-var='time'>10:02</var> UTC Identified - Following the recent 26.1 release, we have identified an issue impacting the Workspot Control service. A newly introduced application feature is not behaving as expected, resulting in an increased volume of system requests. This has led to request queuing and intermittent restarts of the Control service. Our engineering team is actively working on testing and implementing a fix with the highest priority to stabilize the service. Feb <var data-var='date'> 2</var>, <var data-var='time'>09:38</var> UTC Investigating - We are currently experiencing intermittent availability issues with the Workspot Control service. The engineering team is actively working on this issue with top priority. We will share more details as they become available. This is an application‑level issue and not a security incident. We apologize for any inconvenience this may cause.

Workspot Control Experiencing Intermittent Availability

Jan <var data-var='date'>31</var>, <var data-var='time'>03:00</var> UTC Completed - The scheduled maintenance has been completed. Jan <var data-var='date'>31</var>, <var data-var='time'>02:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>14</var>, <var data-var='time'>05:31</var> UTC Scheduled - This release will require an update window of up to 10 minutes. During this window, administrators will not be able to log in to Control, and end users will not be able to launch new non-persistent desktop sessions. Existing end-user sessions will not be impacted, and end users can launch persistent desktops.

Is Workspot down?

Workspot status is UP

Lastest published events

Workspot EU Control Upgrade to R26.6 on July 7th at 0530 UTC

Workspot US Control Upgrade to R26.6 on July 3rd at 0200 UTC

Workspot US Trends Upgrade to R2.8.0 on June 30th at 03:30 AM UTC

Workspot Services, Components and Regions

Recent Workspot events

Workspot EU Control Upgrade to R26.6 on July 7th at 0530 UTC

Workspot US Control Upgrade to R26.6 on July 3rd at 0200 UTC

Workspot US Trends Upgrade to R2.8.0 on June 30th at 03:30 AM UTC

Workspot EU Trends Upgrade to R2.8.0 on June 27th at 03:30 AM UTC

Workspot EU Watch Upgrade to R6.7.0 on June 23rd, at 03:30 AM UTC

Workspot US Watch Upgrade to R6.7.0 on June 20th, at 03:30 AM UTC

Get your FREE account now,
5 monitors included!

Is Workspot down?

Workspot status is UP

Lastest published events

Workspot EU Control Upgrade to R26.6 on July 7th at 0530 UTC

Workspot US Control Upgrade to R26.6 on July 3rd at 0200 UTC

Workspot US Trends Upgrade to R2.8.0 on June 30th at 03:30 AM UTC

Workspot Services, Components and Regions

Recent Workspot events

Workspot EU Control Upgrade to R26.6 on July 7th at 0530 UTC

Workspot US Control Upgrade to R26.6 on July 3rd at 0200 UTC

Workspot US Trends Upgrade to R2.8.0 on June 30th at 03:30 AM UTC

Workspot EU Trends Upgrade to R2.8.0 on June 27th at 03:30 AM UTC

Workspot EU Watch Upgrade to R6.7.0 on June 23rd, at 03:30 AM UTC

Workspot US Watch Upgrade to R6.7.0 on June 20th, at 03:30 AM UTC

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!