Major incident
Kaseya: Datto BCDR - Server3824 (Germany Region) - Degraded Node Functionality
Aug 25, 2026, 16:09 UTC
started
16:44 UTC
resolved September 3, 2026
9 days
duration
Affected: Off-Site Synchronization, Off-Site Recovery
Current status of Kaseya: Partial outage — live Kaseya status
Timeline
- Aug 25, 2026, 16:09 UTCidentifiedWe are aware of a problem where Datto BCDR users paired to Server3824 will experience a service degradation affecting offsite performance and related operations. The Kaseya Engineering Team has identified the issue and is working towards a resolution. 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/
- Sep 3, 2026, 16:44 UTCresolvedThis incident has been resolved.
Updates as published by Kaseya (original).
Other services with incidents at the same time
- LiveRamp External 16:43 UTC · Incident Resolved for Cleanroom - Habu API via Grafana
- Cloudsmith 16:38 UTC · Request latency and timeout
- Pinecone 15:50 UTC · [SERVERLESS][GCP][us-central1] 5xx errors on some read and write requests
More Kaseya incidents
- October 26, 2026 Datto Endpoint Backup - Backups not running on some Endpoint Backup Servers
- October 26, 2026 Datto SaaS Protection - Service disruption for customers hosted on node 'aue1-bfyii-1533'
- October 26, 2026 Datto SaaS Protection - Backup Performance Degradation For Customers Hosted On Pod 'aue2-saas-p2'
- October 24, 2026 Datto BCDR (Business Continuity and Disaster Recovery) - Node: use1-dtc-server-118 is inaccessible - Preventing access to Backups/ Screenshots/ Restores.
- October 23, 2026 Datto RMM v15.2.0 - Pinotage (EU1) - Device Filter Issue
- October 22, 2026 Datto SaaS Protection - Service disruption for customers hosted on node 'gbe2-bfyii-1555'