We are still working on recovering back to a serviceable state and expect to have a more substantial update within another two hours.
Last update on
We have identified a mitigation for the Exchange Online backup authentication errors related to Exchange Web Services (EWS) access. Backups are succeeding for customers who enable EWS at both the organization and mailbox levels and allow time for Microsoft 365 replication to complete. We continue to work with Microsoft to investigate a small number of edge cases where issues may persist, and we will provide further updates as more information becomes available. More information on the workaround can be found here: https://www.veeam.com/kb479 "https://www.veeam.com/kb4796": https://www.veeam.com/kb4796
Last update on
Two Availability Zones in AWS me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. We strongly recommend that customers with workloads in AWS me-central-1 act now to move their clusters to alternate regions instead of waiting for full availability to be restored. There are currently no recovery options available for data that is only present in the AWS me-south-1 region. We continue to assist customers in their chosen remediation path to the extent possible. Customers running workloads in the Middle East should consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may continue to extend their backup snapshot expirations in me-central-1 as needed. We will continue with a weekly status post update cadence, and provide another update by April 8 at 16:00 UTC, or sooner if new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface
Last update on
We’re continuing to investigate this issue and will provide an update as soon as one is available.
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
Veeam
Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)
MongoDB
Advisory: Investigating reports of Azure DevOps access issues when using Microsoft Defender for Cloud
Azure DevOps
Increased Connectivity Issues and API Error Rates
Amazon Web Services
