Major incident

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

Sep 28, 2026, 13:28 UTC
started
18:17 UTC
resolved
4 h 50 min
duration

Affected: Limited Release, America East, America East 2, America East 3, America West, America West 2, America West 3, Australia / New Zealand 4, UK Limited Release (United Kingdom), UK (United Kingdom), UK 2 (United Kingdom), UK03 (United Kingdom), EU1 (English Europe and Asia), Australia / New Zealand, Australia / New Zealand 2, Australia/ New Zealand 3 (Sydney Datacenter), German (Deutsch), Spanish (Español), Report Data Warehouse, AT01

Current status of Kaseya: Partial outage — live Kaseya status

Timeline

  1. Sep 28, 2026, 13:28 UTC
    investigating
    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. Sep 28, 2026, 14:39 UTC
    identified
    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. Sep 28, 2026, 15:34 UTC
    monitoring
    A fix has been implemented and we are monitoring the results.
  4. Sep 28, 2026, 17:08 UTC
    monitoring
    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. Sep 28, 2026, 18:17 UTC
    resolved
    This incident has been resolved.

Updates as published by Kaseya (original).

Other services with incidents at the same time

This was part of a wider event: 51 services reported incidents within the hour.

More Kaseya incidents