Datto incident

Autotask - All Regions - LiveMobile inaccessible on Android Devices, https://autotask.net Certificate Error, and Datto RMM Integration Errors

Major Resolved View vendor source →

Datto experienced a major incident on September 28, 2026 affecting Limited Release and America East and 1 more component, lasting 4h 49m. The incident has been resolved; the full update timeline is below.

Started
Sep 28, 2026, 01:28 PM UTC
Resolved
Sep 28, 2026, 06:17 PM UTC
Duration
4h 49m
Detected by Pingoru
Sep 28, 2026, 01:28 PM UTC

Affected components

Limited ReleaseAmerica EastAmerica East 2America East 3America WestAmerica West 2America West 3Australia / New Zealand 4UK Limited Release (United Kingdom)UK (United Kingdom)

Update timeline

  1. investigating Sep 28, 2026, 01:28 PM UTC

    We are aware of a problem where LiveMobile is inaccessible on Android devices across all regions. The Kaseya Engineering Team is investigating the issue. 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. identified Sep 28, 2026, 02:39 PM UTC

    The issue has been identified and a fix is being implemented. When logging into Autotask on the web, to ensure the best connectivity to your Autotask instance, please double check your configuration to ensure that the zone specific (ww# or ww##) URL is being used.

  3. monitoring Sep 28, 2026, 03:34 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Sep 28, 2026, 05:08 PM UTC

    Monitoring post release detected an issue with the Autotask and Datto RMM integration. This issue caused tickets to fail to create from Datto RMM, prevented access to the Autotask integration settings in Datto RMM, and prevented new monitor creation in Datto RMM when the option to "Create a Ticket" was set. A new fix has been deployed to correct these issues and we will continue to monitor the results.

  5. resolved Sep 28, 2026, 06:17 PM UTC

    This incident has been resolved.