Major incident
MongoDB Cloud: Intermittent 503 Errors on Atlas Admin API and Automation Tooling
Mar 25, 2026, 21:31 UTC
started
13:21 UTC
resolved March 27, 2026
39 h 50 min
duration
Affected: MongoDB Cloud
Current status of MongoDB Cloud: Operational — live MongoDB Cloud status
Timeline
- Mar 25, 2026, 21:31 UTCinvestigatingWe 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.
- Mar 25, 2026, 23:39 UTCmonitoringThe team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.
- Mar 26, 2026, 19:12 UTCmonitoringWe 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.
- Mar 27, 2026, 13:21 UTCresolvedWe are no longer seeing intermittent spikes in HTTP 503 errors.
Updates as published by MongoDB Cloud (original).
More MongoDB Cloud incidents
- October 20, 2026 GCP Availability Zone europe-west2-b connectivity issues
- October 9, 2026 Issue impacting Atlas Search availability on certain clusters
- October 9, 2026 Admin Admin API: Intermittent Increase in 5xx errors
- October 2, 2026 MongoDB Charts: Infinite login loop when creating new Charts projects
- October 1, 2026 Trigger processing may be delayed globally
- September 30, 2026 Delays in Atlas cluster management operations