MongoDB incident

Intermittent 503 Errors on Atlas Admin API and Automation Tooling

Major Resolved View vendor source →

MongoDB experienced a major incident on March 25, 2026 affecting MongoDB Cloud, lasting 1d 15h. The incident has been resolved; the full update timeline is below.

Started
Mar 25, 2026, 09:31 PM UTC
Resolved
Mar 27, 2026, 01:21 PM UTC
Duration
1d 15h
Detected by Pingoru
Mar 25, 2026, 09:31 PM UTC

Affected components

MongoDB Cloud

Update timeline

  1. investigating Mar 25, 2026, 09:31 PM 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.

  2. monitoring Mar 25, 2026, 11:39 PM UTC

    The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.

  3. monitoring Mar 26, 2026, 07:12 PM 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.

  4. resolved Mar 27, 2026, 01:21 PM UTC

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