As of March 25, we have deployed an update globally and are seeing stable operation. While no new instances of the error are being observed, we are continuing follow-up work to ensure all previously impacted scenarios are fully resolved. An update on this work will be provided as soon as possible.
Last update on
The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.
Last update on
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
Monitors
Intermittent SharePoint item download failures in Veeam Data Cloud for Microsoft 365
Veeam
Increased Connectivity Issues and API Error Rates
Amazon Web Services