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
SSO is experiencing degraded functionality because of an upstream provider. We are monitoring, and users may need to retry when authenticating with their IdP.
Last update on
Exclaimer Engineers are continuing to monitor the situation at this time. The rate of messages being deferred due to the connecting server failing to provide the email has dropped substantially as well since Monday. We are continuing to reach out to Microsoft to discuss the issue and obtain a complete understanding of it, and to confirm that the issue has been addressed.
Last update on
Monitors
Increased Connectivity Issues and API Error Rates
Amazon Web Services
1Password
Possible Routing issues within MEA & US region for Microsoft Customers
Exclaimer
Freshservice
StatusGator