Changes / MongoDB Atlas / Intermittent 503 Errors on Atlas Admin API and Automation Tooling

MongoDB Atlas: Major incident: Intermittent 503 Errors on Atlas Admin API and Automation Tooling

Summary

MongoDB Atlas reported a major degradation: intermittent HTTP 503 errors affected Atlas Admin API and automation tooling such as Terraform; requests typically succeeded on retry, while database connectivity remained healthy. It lasted 39 h 50 min, from 2026-03-25 21:31 UTC to 2026-03-27 13:21 UTC. MongoDB identified the root cause and applied a fix, without specifying details.

Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.

Major incidentLabel: degradation (model (Jev), 70%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Intermittent 503 Errors on Atlas Admin API and Automation Tooling
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-03-25 21:31 UTC
AddedResolved time#5
Before: not present
After: 2026-03-27 13:21 UTC
AddedAffected components#6
Before: not present
After: MongoDB Cloud
AddedUpdateinvestigating#7
Before: not present
After: 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.
AddedUpdatemonitoring#8
Before: not present
After: The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.
AddedUpdatemonitoring#9
Before: not present
After: 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.
AddedUpdateresolved#10
Before: not present
After: We are no longer seeing intermittent spikes in HTTP 503 errors.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Intermittent 503 Errors on Atlas Admin API and Automation Tooling (this change)
MongoDB Atlas reported a major degradation: intermittent HTTP 503 errors affected Atlas Admin API and automation tooling such as Terraform; requests typically succeeded on retry, while database connectivity remained healthy. It lasted 39 h 50 min, from 2026-03-25 21:31 UTC to 2026-03-27 13:21 UTC. MongoDB identified the root cause and applied a fix, without specifying details.
Major incident

All MongoDB Atlas changes → · MongoDB Atlas profile · Markdown · JSON