---
id: "INC-mongodb-7g5qmxgkc2y4"
kind: "incident"
aliases: []
title: "MongoDB Atlas: Impaired Cluster Operations \u2013 AWS me-central-1 (United Arab Emirates)  and AWS me-south-1 (Bahrain)"
severity: "high"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "MongoDB Atlas", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["database", "incident", "mongodb", "ops", "vendor"]
not_affected_if: []
published_at: "2026-03-01T13:48:14+00:00"
first_seen_at: "2026-10-23T19:12:22+00:00"
updated_at: "2026-10-25T05:37:22+00:00"
sources: [{"source": "statuspage", "url": "https://stspg.io/mg7m971rdhw8", "first_seen_at": "2026-10-23T19:12:22+00:00"}]
---

# MongoDB Atlas: Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates)  and AWS me-south-1 (Bahrain)

## Affected

- vendor:MongoDB Atlas affected ? fixed ?

## Timeline

- 2026-10-23T19:12:22+00:00 statuspage https://stspg.io/mg7m971rdhw8

## From the sources

While we are marking this issue as resolved, the issue actually remains ongoing. We are marking this as resolved to improve the experience of users on our status page. The latest information from AWS remains available at https://health.aws.amazon.com/health/status
We will update this post as necessary. Thanks in advance for your understanding.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_