MongoDB incident

MongoDB Atlas Admin API: Temporary failures for tools using older API versions

Notice Resolved View vendor source →
Started
Mar 11, 2026, 10:00 AM UTC
Resolved
Mar 02, 2026, 12:00 PM UTC
Duration
Detected by Pingoru
Mar 11, 2026, 10:00 AM UTC

Update timeline

  1. resolved Mar 11, 2026, 10:00 AM UTC

    Users may have seen tools and integrations that rely on older MongoDB Atlas Admin API versions (for example, 2023-01-01 and 2023-02-01) start failing with HTTP 410 responses indicating that the requested version was no longer available. This affected workflows using the MongoDB Atlas Admin API through the Terraform provider, the Atlas CLI, and custom automation. This behavior was triggered by our planned retirement process for older API versions, but the resulting user impact was unintended because these versions were still in active use. We have extended the end-of-life date for the affected API versions to mid-2027 (tentative date 2027-07-01) and deployed a configuration change to restore compatibility for these workflows. All affected tools and integrations should now be operating normally & will be updated prior to the modified end-of-life-date. From 2026-03-01 00:00 UTC to 2026-03-02 12:01 UTC, users relying on these older API versions may have experienced failed requests and associated automation errors. No user action is required. Previously failed operations can be retried and should now succeed.

Looking to track MongoDB downtime and outages?

Pingoru polls MongoDB's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when MongoDB reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track MongoDB alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring MongoDB for free

5 free monitors · No credit card required