← Back to MongoDB Atlas History
major✓ Resolved

Intermittent 503 Errors on Atlas Admin API and Automation Tooling

MongoDB AtlasWed, Mar 25, 2026, 09:31 PM
Status
resolved
Duration
1d 15h
Updates
3
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedFri, Mar 27, 2026, 01:25 PM
This incident has been resolved.
monitoringThu, Mar 26, 2026, 07:12 PM
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.
monitoringWed, Mar 25, 2026, 11:39 PM
The team has identified the root cause of intermittent spikes of HTTP 503 errors and has applied a fix.
investigatingWed, Mar 25, 2026, 09:31 PM
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.

📊 TECHNICAL DETAILS

Internal ID
209774b0-2789-42ad-81bd-fa4043ac93f2
External ID
gch8hbs1yfz5
🕐 Started
Wed, Mar 25, 2026, 09:31 PM
🔄 Last Updated
Fri, Mar 27, 2026, 01:25 PM
✓ Resolved
Fri, Mar 27, 2026, 01:25 PM
MAJOR
Impact Level
1d 15h
Total Duration
3
Status Updates
Affected Components
MongoDB Cloud
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed