Changes / MongoDB Atlas / Impaired Cluster operations in AWS me-central-1 and AWS me-south-1

MongoDB Atlas: Major incident: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1

Summary

MongoDB Atlas reported major impairment of cluster operations in AWS me-central-1 and AWS me-south-1, affecting MongoDB Cloud, starting 2026-09-03 16:44 UTC. The incident remained open under monitoring when archived; the recorded open duration was 2 minutes, with no cause or fix stated.

Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.

Major incidentLabel: degradation (model (Jev), 82%)Changed Detected Source: stspg.io

What changed

AddedTitle#1
Before: not present
After: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: monitoring
AddedStart time#4
Before: not present
After: 2026-09-03 16:44 UTC
AddedAffected components#5
Before: not present
After: MongoDB Cloud
AddedUpdatemonitoring#6
Before: not present
After: Please follow <a href="https://status.mongodb.com/incidents/7g5qmxgkc2y4">the original status post</a> for updates on AWS me-central-1 and AWS me-south-1 issues.
AddedUpdatemonitoring#7
Before: not present
After: We are continuing to monitor for any further issues.

First version of this incident archived by Rewindex. View the live incident.

History of this incident

When (UTC)ChangeKind
Major incident: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1 (this change)
MongoDB Atlas reported major impairment of cluster operations in AWS me-central-1 and AWS me-south-1, affecting MongoDB Cloud, starting 2026-09-03 16:44 UTC. The incident remained open under monitoring when archived; the recorded open duration was 2 minutes, with no cause or fix stated.
Major incident

All MongoDB Atlas changes → · MongoDB Atlas profile · Markdown · JSON