Intermittent 503 Errors on Atlas Admin API and Automation Tooling
Mar 25, 21:31 UTCMar 27, 13:21 UTC
Duration
39h 50m
Impact
Major
Root cause
Not disclosed
MongoDB, 90 days
12 incidents
Affected
MongoDB Cloud
Final update
We are no longer seeing intermittent spikes in HTTP 503 errors.
Timeline
- Resolved · Mar 27, 13:21 UTC
We are no longer seeing intermittent spikes in HTTP 503 errors.
- Monitoring · Mar 26, 19:12 UTC
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.
- Monitoring · Mar 25, 23:39 UTC
The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.
- Investigating · Mar 25, 21:31 UTC
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.
More from MongoDB
Full historyGCP Availability Zone europe-west2-b connectivity issueslasted 12h 36mIssue impacting Atlas Search availability on certain clusterslasted 1h 48mAdmin Admin API: Intermittent Increase in 5xx errorslasted 2h 35mMongoDB Charts: Infinite login loop when creating new Charts projectslasted 5hTrigger processing may be delayed globallylasted 5h 13mDelays in Atlas cluster management operationslasted 2h 10m