Live  /  MongoDB Cloud  /  Incident

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

MongoDB Cloud · mongodb.comMajor incidentResolved2026-06-03 15:46 UTC
Public — what happened

Summary

MongoDB Cloud reported a major disruption to Atlas clusters running in two Amazon Web Services regions in the Middle East, me-central-1 in the United Arab Emirates and me-south-1 in Bahrain, beginning on March 1, 2026 at 19:30 UTC. The company said both regions had been damaged, leaving UAE workloads seriously impaired and Bahrain workloads fully down, unable to be changed, moved, or restored from backup, with no way currently to recover data stored only in Bahrain. Citing an AWS update from April 30, MongoDB said recovery could take several months and urged customers in the UAE region to relocate clusters to other regions now rather than wait. The incident is listed as being monitored, and MongoDB said it would post further updates only when new information arrives.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach MongoDB Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for MongoDB Cloud: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the MongoDB Cloud report →

More from MongoDB Cloud

The full archive is on the MongoDB Cloud status & history page.

Related: MongoDB Cloud status & history. SquidGrid is not affiliated with MongoDB Cloud.