Vendor reports: partial outageResolved · vendor status “resolved”Official status API
Datto SaaS Protection - M365 Backup Performance Degradation - Post-Graph Migration
Reported by Kaseya · Cloud & Infrastructure · source last read 4 min ago
- Vendor start
- Sep 30, 2026, 16:37 UTC
- Vendor's clock
- Resolved
- Nov 2, 2026, 16:03 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 32 d 23 h
- 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: SaaS Protection Backups.[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-11-02 16:03 UTC · summary s1, evidence 1f78f47789f599a6
Evidence (7)
- E1Kaseya reports partial outage. (vendor) source (opens in a new tab)
- E2Vendor title: "Datto SaaS Protection - M365 Backup Performance Degradation - Post-Graph Migration". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-09-30 16:37 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6Components the vendor attached: SaaS Protection Backups. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2026-11-02 16:03 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: SaaS Protection Backups
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 30, 2026, 16:37 UTCVendor-reported startVendor time
- Nov 2, 2026, 16:03 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.