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
A fix has been implemented and we are monitoring the results.
Last update on
Our engineering teams are continuing to make progress on resolving the display issue within the Investigate dashboard. While remediation is in progress, we anticipate it may take a few more days to fully resolve. We will provide further updates as they become available.
Last update on
A fix has been implemented and we are monitoring the results.
Last update on
We want to make you aware of a technical issue related to last night’s automatic update to Mac Agent version 3.7.3. During the auto-update process, an issue was triggered that can cause high memory usage and intermittent internet connectivity drops on certain Mac devices. We understand the disruption this may cause in your environment and sincerely apologize for the inconvenience. Our product and engineering teams are actively working to resolve the issue as quickly as possible. Temporary Workarounds Until a permanent fix is released, there are two options available: Recommended Remediation: The most effective solution is to fully uninstall and then reinstall the 3.7.3 agent on affected devices. Interim Workaround: If an immediate reinstall is not possible, you may temporarily move affected devices to DNS filtering mode until the reinstall can be completed. It’s important to note that version 3.7.3 itself is stable when installed directly or manually deployed via your MDM. The issue is specific to the automatic update process. If you need assistance performing the manual installation, switching to DNS mode, or have any questions, please contact our Support team and we will be happy to help. Thank you for your patience while we work to resolve this issue.
Last update on
Monitors
Amazon Web Services
[Cisco Umbrella/Secure Connect]-Dashboard– DNS Query Volume Display Degradation
Cisco Umbrella
Mac Agent 3.7.3 Connectivity Issue and Temporary Workarounds
Shakopee Infinite Campus
StatusGator