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 aware of a low-frequency issue where certain legitimate files may be unexpectedly quarantined by a behavioral detection component. What’s happening In rare cases, a behavioral detection module may briefly activate during endpoint startup before policy settings are fully applied. During this short window, files that would normally be allowed may be flagged and quarantined. Customer impact Low probability, but non-zero Quarantined files may not generate alerts in the console Files cannot currently be restored directly from the portal What we’re doing Implementing a fix to ensure this component does not activate during startup Rolling out updates in a controlled manner Actively monitoring to ensure the issue is fully resolved What you should do If you believe this has impacted your environment: Contact Support Our team can assist with restoring files from quarantine !!! Important !!! Do not remove AV licenses from affected devices, as this may result in permanent deletion of quarantined files. Next update We will share progress as rollout completes and the fix is fully deployed.
Last update on
We are aware of a low-frequency issue where certain legitimate files may be unexpectedly quarantined by a behavioral detection component. What’s happening In rare cases, a behavioral detection module may briefly activate during endpoint startup before policy settings are fully applied. During this short window, files that would normally be allowed may be flagged and quarantined. Customer impact Low probability, but non-zero Quarantined files may not generate alerts in the console Files cannot currently be restored directly from the portal What we’re doing Implementing a fix to ensure this component does not activate during startup Rolling out updates in a controlled manner Actively monitoring to ensure the issue is fully resolved What you should do If you believe this has impacted your environment: Contact Support Our team can assist with restoring files from quarantine !!! Important !!! Do not remove AV licenses from affected devices, as this may result in permanent deletion of quarantined files. Next update We will share progress as rollout completes and the fix is fully deployed.
Last update on
Monitors
Increased Connectivity Issues and API Error Rates
Amazon Web Services
Datto Status
ConnectWise Control Status
StatusGator