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 aware of a problem where outbound email in EGD to Microsoft Domains is experiencing high deferral rates and are currently monitoring the situation.
Last update on
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar 06, 2026 - 00:15 UTC
Last update on
We have deployed a fix that has resolved the issue in Schoology. We will continue to monitor the application to ensure consistent performance and critical functionality remains intact as expected.
Last update on
We are seeing improvements and working toward full resolution.Current status and actions being taken: We have cleared the message backlog and restored normal processing. Most activity has now completed, and the remaining work is progressing as expected. We will continue monitoring as the remaining scheduled activity runs. Estimated time to resolution: No ETA at this time.Scope: This issue isn't affecting any specific region, but a percentage of users may be affected.Current impact to end users: Developers may not receive responses when @mentioning an app to execute an action in a Slack channel, org admins will observe delays with upcoming/planned migrations, and mobile push notifications may not deliver.Known workarounds: No known workarounds at this time. We will provide the next update as we make further progress or if significant developments occur.
Last update on
We have observed a recovery in MMS delivery from a subset of Twilio Long Codes to Altice network subscribers in the United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
Last update on
We are continuing to work on a fix for this issue and will provide updates as soon as there is more information to share.
Last update on
Monitors
Amazon Web Services
Apple
Email Gateway Defense - Outbound email to Microsoft Domains is experiencing high deferral rates
Barracuda
Schoology
Slack
StatusGator