Impact: Some Atlas customers with deployments in the AWS me-central-1 (United Arab Emirates) region may experience delays in cluster operations (for example, creating, scaling, or modifying clusters and infrastructure-level maintenance tasks). Root cause: AWS is reporting connectivity and power issues affecting APIs and instances in a single Availability Zone in the me-central-1 Region, which can cause increased errors and latency for some AWS services and workflows. For the latest details from AWS, see the AWS Health Dashboard. What you might see: - Cluster create/scale/modify operations remaining in a pending or in-progress state longer than usual - Slower completion of some maintenance and infrastructure operations in the affected region Our actions: - Monitoring the AWS incident and Atlas fleet behavior in me-central-1 Customer action: No action is required at this time. We expect delayed operations to complete as AWS resolves the underlying issue. If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support. Next update: We will provide updates on this page as AWS progresses mitigation or if we observe any change in impact to Atlas customers.
Started
13:48 UTC
Duration
Lasted 186d 3h
Source
IsDown
Next time
MongoDB is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: MongoDB Cloud
What happened?
Impact: Some Atlas customers with deployments in the AWS me-central-1 (United Arab Emirates) region may experience delays in cluster operations (for example, creating, scaling, or modifying clusters and infrastructure-level maintenance tasks). Root cause: AWS is reporting connectivity and power issues affecting APIs and instances in a single Availability Zone in the me-central-1 Region, which can cause increased errors and latency for some AWS services and workflows. For the latest details from AWS, see the AWS Health Dashboard. What you might see: - Cluster create/scale/modify operations remaining in a pending or in-progress state longer than usual - Slower completion of some maintenance and infrastructure operations in the affected region Our actions: - Monitoring the AWS incident and Atlas fleet behavior in me-central-1 Customer action: No action is required at this time. We expect delayed operations to complete as AWS resolves the underlying issue. If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support. Next update: We will provide updates on this page as AWS progresses mitigation or if we observe any change in impact to Atlas customers.
