The Kaseya Engineering team has implemented mitigation measures, and all affected platforms are actively processing a backlog of device sync actions. We continue to see steady progress in reducing the queue; however, additional time is required to fully process the remaining backlog. Our teams will continue monitoring system performance throughout the weekend and will provide updates as significant progress is made. To receive notifications about future maintenance events and service updates, subscribe to the Kaseya Status Page.
We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-az1 and mec1-az3). Since the disruption began in March, most customers have been able to re-establish their operations in other Regions by restoring backups or copying data that remained accessible. AWS Support remains available to help customers who need assistance moving their applications to alternate Regions. We remain committed to supporting our customers in the UAE. We are working on replacing the affected infrastructure and will provide an update on the restoration of our services in the coming months. We have notified the relevant authorities and continue to work with them toward that goal.
Monitors
Datto RMM - Version 15.2.0 (Pinotage, Syrah, Zinfandel, Concord) - Autotask Integration Device Sync Delays
Kaseya
Amazon Web Services