Welcome to the service status page. Here, you can stay up to date with the operational status of all your key services. Subscribe to receive instant notifications when incidents or maintenance occur. If you’re experiencing any issues not reflected here, please report them, or contact our support team directly for assistance. We’re committed to keeping everything running smoothly for you!
We have a scheduled maintenance period March 3rd between 01:00 AM and 03:00 AM. During this scheduled maintenance period, please note that x360Recover Manager (my.axcient.net) may be temporarily unavailable. Thank you for your continued partnership and patience as we release a new version of the product.
Last update on
According to AWS, two Availability Zones in me-central-1 (UAE) and one Availability Zone in me-south-1 (Bahrain) continue to experience outages. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. CURRENT IMPACT Atlas clusters deployed only in me-central-1 may be fully unavailable. For clusters operating solely in me-central-1, backup operations in this region are impaired. Clusters and backups should remain operational in me-south-1 at this time. Clusters in me-south-1 may be running at reduced capacity due to zonal constraints. AWS has indicated an extended resolution timeline for service in the impacted Regions and Availability Zones. RECOMMENDED CUSTOMER ACTIONS If you have a multi-region configuration that includes a healthy secondary region, we recommend routing application traffic to that secondary region. If you have clusters in me-south-1 taking backups, we recommend enabling "Additional Snapshot Copies Policy" to a different region. If you have time-sensitive production changes or operations that are blocked and need urgent assistance, please contact MongoDB Support via the Support Portal, Support Chat or in-product support. WHAT WE ARE DOING We recognize the severity of this situation and the impact it may have on your workloads. The situation continues to evolve, and we are closely monitoring AWS status and regional health signals. We are validating Atlas behavior across affected and unaffected regions, and working to mitigate customer impact where possible. We will provide further updates as circumstances continue to change.
Last update on
Our work on this issue is still ongoing.Current status and actions being taken: International Data Residency (IDR) customers continue to experience search disruptions due to a regional incident affecting our third-party provider, Amazon Web Services. This issue is related to the broader Salesforce incident currently underway. We are actively working to restore service, but there is no estimated time of recovery. Conditions at the impacted facilities, including loss of power and cooling, continue to affect progress. We are closely monitoring the situation, and will provide further updates as new information becomes available.Current impact to end users: International Data Residency (IDR) users in the Middle East (Dubai) region may experience degraded search performance or search failures. Services for other users in the region are operating normally. We continue to monitor the situation closely and will provide updates as more information becomes available.
Last update on
We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. AWS infrastructure is designed to be highly resilient, but given the uncertainty of the current situation, we encourage our customers to replicate Amazon S3 and critical data from the ME-SOUTH-1 Region to another AWS Region. 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. We will provide another update by March 3 at 3:00 AM PST, or sooner if new information becomes available. For more information on Cross-Region Replication, refer [1]. For more information on S3 Batch Replication, see [2]. For a simple script to quickly set up and start S3 Replication, see [3]. If you have questions or concerns, please contact AWS Support [4]. [1] <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.html">https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.html</a> [2] <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html">https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html</a> [3] <a href="https://github.com/awslabs/aws-support-tools/blob/master/S3/Setup_Replication/setup_replication.py">https://github.com/awslabs/aws-support-tools/blob/master/S3/Setup_Replication/setup_replication.py</a> [4] <a href="https://aws.amazon.com/support">https://aws.amazon.com/support</a>
Last update on
Monitors
Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)
MongoDB
Increased Connectivity Issues and API Error Rates
Amazon Web Services
StatusGator