Vendor reports: operationalOpen · vendor status “monitoring”Official status API
Autotask – Precautionary Suspension of N-able Integrations
Reported by Kaseya · Cloud & Infrastructure · source last read just now
- Vendor start
- Nov 9, 2026, 20:52 UTC
- Vendor's clock
- Resolved
- Not yet
- Still open
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- Not available
- Needs both vendor times
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.
- When it will be resolved: no estimate is shown unless the vendor publishes one on its page.
Last update in these facts: 2026-11-09 20:52 UTC · summary s1, evidence 8fcd4bbf9d280e69
Evidence (7)
- E1Kaseya reports operational. (vendor) source (opens in a new tab)
- E2Vendor title: "Autotask – Precautionary Suspension of N-able Integrations". (vendor) source (opens in a new tab)
- E3Vendor status word: "monitoring". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-11-09 20:52 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)
- E7Not resolved by the vendor yet. (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.
What to check on your side
Verification steps only. Statuswall cannot see your systems.
- Check resource health in the regions named by the vendor, and in your other regions for comparison.
- Separate control-plane actions (deploys, scaling, console) from data-plane traffic: they often fail differently.
- If you run multi-region or failover, confirm what your own health checks report before acting.
- Check error rates, latency and timeouts in your own monitoring for requests that depend on Kaseya.
- Look at synthetic checks and alerts that exercise Kaseya.
- Compare with recent deploys on your side, so a coincidental change is not blamed on the vendor.
- Follow the vendor's official incident page for scope changes and resolution.
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.
- Nov 9, 2026, 20:52 UTCVendor-reported startVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.