We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). We continue to make progress on recovery efforts across multiple workstreams. For Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be successfully retrieved, and we continue to work on reducing GET error rates for objects written prior to the event. Full recovery of GET operations for pre-existing data remains dependent on restoring the affected infrastructure. For Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery; we expect to see improvement over the coming hours. As these foundational services recover, dependent services — including AWS Lambda, Amazon Kinesis, Amazon CloudWatch, and Amazon RDS — will follow. Amazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region and will be relaxed as foundational service recovery and capacity allow. The AWS Management Console is operational, though customers may continue to experience errors on certain pages as underlying services work through their recovery. With the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center. We continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.
Last update on
We are still seeing major impact in the ME region making Asana services unavailable to users whose data is stored in that region. We are continuing to monitor the situation. The cause is widespread AWS incidents affecting the infrastructure in the Middle East region: https://health.aws.amazon.com/health/status
Last update on
We are continuing to address the impact on Backup-Restore jobs within the me-central-1 and me-south-1 AWS regions. Our engineering team is collaborating with AWS to achieve a complete recovery of the affected regional services. We are observing preliminary signs of stabilization, however we are taking a cautious approach to ensure data integrity and a full restoration. We remain committed to transparency and will provide further updates as soon as actionable information becomes available from AWS. Please feel free to contact the Druva support team at support.druva.com. Druva Support
Last update on
We are continuing our efforts to restore services. Completing this large-scale and complex recovery operation safely and thoroughly requires a considerable amount of time. We have identified and initiated a parallel workstream to streamline and accelerate the restoration process. Workstream 1 – Primary database copy to Sweden The primary process of copying database data from the current environment to the Sweden region continues to progress. This recovery path remains active to ensure the complete dataset can be retrieved. Workstream 2 – Database recovery via AZ1 infrastructure Step 1 - Data Transfer (In Progress): Teams are actively copying data to a recovery environment in Sweden. The primary database transfer is approximately 46% complete and progressing slowly but steadily. Several critical data components, including transactional data, encryption keys, and various platform services have been successfully transferred or are now in progress. Step 2 - Database Rebuild (In Progress): Teams have begun preparing to rebuild and validate the database environment, ensuring data integrity and completeness once transfers are complete. Step 3 - Service Restoration (Pending): Once the first two steps are finished, teams will rebuild the necessary platform components before bringing customer environments back online. Due to the unprecedented scale and technical complexity of reconstructing and thoroughly validating these systems, this recovery will take significant time to complete. We do not yet have a specific timeline for full-service restoration. We will continue to provide regular updates as progress continues.
Last update on
Monitors
Amazon Web Services
Druva inSync
Tungsten Automation/Printix
StatusGator