Skip to content
MongoDB · Data and observabilityMar 25, 2026, 21:31 UTC

Intermittent 503 Errors on Atlas Admin API and Automation Tooling

MajorNot disclosedUpdated 18h ago
Mar 25, 21:31 UTCMar 27, 13:21 UTC
Duration
39h 50m
Impact
Major
Root cause
Not disclosed
MongoDB, 90 days
19 incidents
Affected
MongoDB Cloud
Status page

Final update

We are no longer seeing intermittent spikes in HTTP 503 errors.

Timeline

  1. Resolved · Mar 27, 13:21 UTC
    We are no longer seeing intermittent spikes in HTTP 503 errors.
  2. 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.
  3. 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.
  4. 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 history

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.