Incident History

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.

This incident has been resolved.

This incident has been resolved. Email notifications are being sent successfully.

While we are marking this issue as resolved, the issue actually remains ongoing. We are marking this as resolved to improve the experience of users on our status page. The latest information from AWS remains available at https://health.aws.amazon.com/health/status We will update this post as necessary. Thanks in advance for your understanding.

This incident has been resolved.

The issue has been resolved

This incident has been resolved.

The DNS records have been backfilled and clusters that had these IP addresses should be recovered.

We have identified and resolved the issue. Atlas UI will load without a delay now.

This incident has been resolved.