← Live dashboard

Intermittent 503 Errors on Atlas Admin API and Automation Tooling

ResolvedmajorOfficial source confirmedSpecific component onlyFirst recorded update Mar 25, 2026, 09:31 PM · Resolved Mar 27, 2026, 01:21 PM

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

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with MongoDB Atlas now? Check the current status

Affected services

MongoDB Cloud

Updates (4)

  1. Mar 27, 2026, 01:21 PM
    Intermittent 503 Errors on Atlas Admin API and Automation Tooling

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

    MongoDB Atlas ↗
  2. Mar 26, 2026, 07:12 PM
    Intermittent 503 Errors on Atlas Admin API and Automation Tooling

    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.

    MongoDB Atlas ↗
  3. Mar 25, 2026, 11:39 PM
    Intermittent 503 Errors on Atlas Admin API and Automation Tooling

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

    MongoDB Atlas ↗
  4. Mar 25, 2026, 09:31 PM
    Intermittent 503 Errors on Atlas Admin API and Automation Tooling

    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 inves

    MongoDB Atlas ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow MongoDB Atlas's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.