Vendor reports: partial outageResolved · vendor status “resolved”Official status API
Autotask - All Regions - LiveMobile inaccessible on Android Devices, https://autotask.net Certificate Error, and Datto RMM Integration Errors
Reported by Kaseya · Cloud & Infrastructure · source last read just now
- Vendor start
- Sep 28, 2026, 13:28 UTC
- Vendor's clock
- Resolved
- Sep 28, 2026, 18:17 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 4 h 50 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
- Components: Limited Release - LR01, United Kingdom Limited release - UKLR01, America East 1 - AE01, America East 2 - AE02, America East 3 - AE03, America West 1 - AW01, America West 2 - AW02, America West 3 - AW03, Australia / New Zealand - AU01, Australia / New Zealand 2 - AU02, Australia/ New Zealand 3 - AU03, Australia / New Zealand 4 - AU04, United Kingdom 1 - UK01, United Kingdom 2 - UK02, United Kingdom 3 - UK03, Europe and Asia - EU01, German (Deutsch) - DE01, Spanish (Español) - ES01, Report Data Warehouse.[E6]
What is unknown
- Which regions are affected: the vendor did not say.[E5]
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2026-09-28 18:17 UTC · summary s1, evidence 0163afb6cbd151c2
Evidence (7)
- E1Kaseya reports partial outage. (vendor) source (opens in a new tab)
- E2Vendor title: "Autotask - All Regions - LiveMobile inaccessible on Android Devices, https://autotask.net Certificate Error, and Datto RMM Integration Errors". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-09-28 13:28 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6Components the vendor attached: Limited Release - LR01, United Kingdom Limited release - UKLR01, America East 1 - AE01, America East 2 - AE02, America East 3 - AE03, America West 1 - AW01, America West 2 - AW02, America West 3 - AW03, Australia / New Zealand - AU01, Australia / New Zealand 2 - AU02, Australia/ New Zealand 3 - AU03, Australia / New Zealand 4 - AU04, United Kingdom 1 - UK01, United Kingdom 2 - UK02, United Kingdom 3 - UK03, Europe and Asia - EU01, German (Deutsch) - DE01, Spanish (Español) - ES01, Report Data Warehouse. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2026-09-28 18:17 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: Limited Release - LR01, United Kingdom Limited release - UKLR01, America East 1 - AE01, America East 2 - AE02, America East 3 - AE03, America West 1 - AW01, America West 2 - AW02, America West 3 - AW03, Australia / New Zealand - AU01, Australia / New Zealand 2 - AU02, Australia/ New Zealand 3 - AU03, Australia / New Zealand 4 - AU04, United Kingdom 1 - UK01, United Kingdom 2 - UK02, United Kingdom 3 - UK03, Europe and Asia - EU01, German (Deutsch) - DE01, Spanish (Español) - ES01, Report Data Warehouse
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
Kaseya is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Sep 28, 2026, 13:28 UTCVendor-reported startVendor time
- Sep 28, 2026, 18:17 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.