EFSD Dashboard

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.

UPDATE: The root cause of this issue has been identified. Our Engineering team will be testing a potential fix.

The issue has been identified and a fix is being implemented.

Title: Some users conferenced into a Microsoft Teams emergency call may not be automatically muted or able to mute themselves User impact: Users conferenced into a Microsoft Teams emergency call may not be automatically muted or able to mute themselves. More info: Users conferenced into a Microsoft Teams emergency call are also unable to mute themselves and would need to leave the call. Current status: We've initiated deployment of our code change to address the code mismatch causing users to not be automatically muted as expected or being able to mute themselves in emergency calls. We anticipate deployment to be completed by Monday, October 12, 2026, and we aim to provide updates on our timeline to remediation as deployment progresses. Scope of impact: Users conferenced into a Microsoft Teams emergency call and attempting to mute their audio are affected by this issue. This section may be updated as the investigation progresses. Start time: Friday, September 25, 2026, at 8:09 PM UTC Estimated time to resolve: We anticipate impact to be resolved by Monday, October 12, 2026. Root cause: A code mismatch in the components utilized when marking a Microsoft Teams emergency call as a multi-party call is causing the code to mute participants to not be enabled as expected. Next update by: Friday, October 9, 2026, at 11:00 PM UTC

We are currently investigating this issue.

We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.