MongoDB Atlas reported this major-impact incident on its official status page on Mar 25, 2026, 21:31 UTC. It was resolved after 1d 15h.
Right now MongoDB Atlas is operational. Live MongoDB Atlas status →
We are no longer seeing intermittent spikes in HTTP 503 errors.
We continue to monitor our systems for intermittent spikes in 503 HTTP errors following our deployed fix. We will provide another update tomorrow by 3 PM UTC.
The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.
We are currently investigating intermittent spikes of HTTP 503 errors affecting Atlas control plane operations performed via the Atlas Admin API and automation tooling such as Terraform. Impacted requests typically fail for a short period and succeed on retry. Atlas database connectivity and data plane operations remain healthy. Our engineering teams are working to resolve the issue with high urgency and to prevent recurrence. Customers encountering 503 responses are advised to retry failed Admin API and Terraform operations with appropriate retry logic and backoff while we continue our investigation.
Our 5-minute checks didn't record a change in MongoDB Atlas's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
MongoDB Atlas reported 15 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 31m. See MongoDB Atlas's uptime and incident history