Critical incident

Kaseya: DattoRMM - Vidal - Users are unable to access the platform.

Affected: Vidal (US East)

Current status of Kaseya: Partial outage — live Kaseya status

Timeline

1. Sep 1, 2026, 11:37 UTC
   investigating
   We are aware of a problem where users are unable to access the Vidal platform The Kaseya Engineering Team is actively investigating and we will provide updates as more information becomes available. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
2. Sep 1, 2026, 12:35 UTC
   monitoring
   The Kaseya Engineering Team has issued a fix. Service has been restored, and we are monitoring the environment to ensure continued stability.
3. Sep 1, 2026, 15:56 UTC
   resolved
   The issue affecting access to the Datto RMM Vidal platform has been resolved.
4. Oct 20, 2026, 13:41 UTC
   postmortem
   **Root Cause Analysis: Vidal Platform Access Issues from East US Locations** **Summary** On September 1, 2026, between 10:00 UTC and 12:35 UTC, some customers accessing the Vidal platform from East US locations were unable to access the service. The issue was detected at 10:00 UTC following customer reports and internal observations. Service accessibility was restored after the affected cached content was invalidated. **Root Cause** The issue occurred during a platform deployment when requests were temporarily distributed between the previous and newly deployed application versions. Under certain conditions, the application attempted to retrieve a web asset that was not available in the version handling the request. The resulting response was then stored in cache, preventing affected users from successfully loading the Vidal platform. **Incident Timeline** * **Identified:** September 1, 2026, at 10:00 UTC * **Public notification:** September 1, 2026, at 11:37 UTC * **Resolved:** September 1, 2026, at 12:35 UTC **Preventative Measures** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps: * **Enhancements to Application Response Handling:** We have updated the application to return an appropriate response when a requested web asset is unavailable, preventing an incorrect response from being cached. This corrective change has been completed. * **Enhancements to Cache Management:** We have refined our current process on how unavailable application assets are handled so that missing content is not stored in the cache and subsequently returned to users. * **Enhancements to Post-Deployment Validation:** Further strengthen our current post-deployment validation to verify platform accessibility from multiple network paths and locations immediately following a deployment. * **Enhancements to Monitoring and Alerting:** Expand the existing monitoring to identify platform accessibility issues quicker. * **Enhancements to Incident Response:** Enhance current documentation to include additional relevant post-deployment symptoms, potential causes, and validated remediation steps to support faster diagnosis and recovery if similar behavior is observed.

Updates as published by Kaseya (original).