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 09, 2026 - 18:30 UTC
Last update on
This issue has resurfaced and we're actively engaged to resolve the issue as quickly as possible.Current status and actions being taken: We have identified the trigger cause and are working on a comprehensive fix to prevent this from happening again. Estimated time to resolution: We are working urgently to resolve this issue as quickly as possible.Scope: A subset of Enterprise customers using Single Sign-On (SSO) are experiencing intermittent login issues. This is not affecting all users within impacted organizations, and the issue may vary by session. Current impact to end users: Users attempting to log in via SSO may encounter errors requiring them to refresh their browser multiple times before successfully accessing their workspace. Some users may experience a degraded login experience even after gaining access.Known workarounds: We do not have any workarounds at this time.We'll continue to provide updates as significant progress is made.
Last update on
Our monitoring systems have detected a potential issue with Flex agent page. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
Last update on
StatusGator