We are providing an update on the ongoing service disruptions affecting the AWS Middle East (Bahrain) Region (ME-SOUTH-1). We continue to make progress on recovery efforts across multiple workstreams. 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 continuing to address the impact on Backup-Restore jobs within the me-central-1 AWS region. 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
Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Friday, 2026-04-10 09:00 PDT.
Last update on
When clicking on the recalculate button the calculator icon spins indefinitely, and the "Calculated at" timestamp doesn't update. This is a visual bug, all calculations are still being performed as expected. The workaround is refreshing the page. We've classified this issue as a severity 4, and will update at the most every 5 business days.
Last update on
Monitors
Increased Connectivity Issues and API Error Rates
Amazon Web Services
Druva inSync
Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys.
Google Workspace
Tungsten Automation/Printix
StatusGator