Live / MongoDB Cloud / Incident
MongoDB Cloud: Issue impacting Atlas Search availability on certain clusters
MongoDB Cloud · mongodb.comMajor incidentResolved2026-10-09 18:17 UTC
Public — what happened
Summary
MongoDB Cloud reported a major incident on October 9, 2026, beginning at 16:29 UTC, in which some Atlas customers using search and vector search features could lose access to those services. The company said a component that powers search was crashing on certain clusters, and it reported having pinpointed the problem by 16:30 UTC. A fix was rolled out at 17:09 UTC, and MongoDB Cloud marked the incident resolved at 18:17 after a period of monitoring.
Affected
MongoDB Atlas Search
Timeline
- Started — 2026-10-09 16:29 UTC
- Investigating — 2026-10-09 16:29 UTC
- Identified — 2026-10-09 16:30 UTC
- Monitoring — 2026-10-09 17:09 UTC
- Resolved — 2026-10-09 18:17 UTC · 1h 48m after it started
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 42, 2026, our weekly internet health report.