Live / MongoDB Cloud / Incident
MongoDB Cloud: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1
MongoDB Cloud · mongodb.comMajor incidentmonitoring2026-09-03 16:47 UTC
Public — what happened
Summary
MongoDB Cloud reported a major incident affecting cluster operations in two AWS regions, me-central-1 and me-south-1, beginning on 2026-09-03 at 16:44 UTC. The company pointed readers to a separate, earlier status post for ongoing updates and did not describe a cause on this page. As of its last update at 16:47 UTC, MongoDB Cloud said it was still watching for further problems, and the incident had not been marked resolved.
Affected
MongoDB Cloud
Timeline
- Started — 2026-09-03 16:44 UTC
- Monitoring — 2026-09-03 16:44 UTC (2 updates)
- Ongoing at last check.
With SquidGrid — where it starts on the route
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 seeCustomers 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
Covered in The Squid’s Ink, Week 37, 2026, our weekly internet health report.