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
The underlying carrier is working with the affected mobile carrier to resolve the issue. If you are experiencing this issue, please reach out to customer care. The next update will be provided in the morning of April 20th or when a significant change in status occurs.
Last update on
Monitors
Increased Connectivity Issues and API Error Rates
Amazon Web Services
A portion of customers with a 307 area code may be experiencing inbound call failures from a specific mobile provider due to an underlying carrier issue.
RingCentral
Houghton Mifflin Harcourt
Savvas (Success Maker - Easy Bridge)
StatusGator