MongoDB Outage History

MongoDB Cloud experienced impaired cluster operations for 2.6 hours due to a Let's Encrypt certificate authority outage. The service was restored after Let's Encrypt returned to healthy status, with MongoDB continuing to monitor until cluster operations fully normalized.

AWS Availability Zone use1-az4 in the US-EAST-1 region experienced an impairment that affected MongoDB Atlas clusters, causing some cluster nodes to have degraded health and delays in operations like instance scaling and configuration changes. The Atlas system implemented healing actions to restore affected nodes and provisioned new nodes in healthy availability zones while AWS worked to restore full availability. The incident was resolved after 36.1 hours of monitoring and remediation efforts.

MongoDB AWS clusters experienced degraded DNS changes that prevented cluster topology modifications from completing successfully or caused significant delays. The issue was traced to corrupted metadata that disrupted DNS operations and downstream cluster updates. The problem was resolved after 7 hours by patching the faulty metadata, restoring normal DNS functionality and cluster update processes.

MongoDB Atlas experienced degraded performance affecting a subset of backup export jobs for 23.2 hours. The issue caused failures in backup export functionality while cluster health and data remained unaffected. The problem was resolved after implementing a fix and monitoring the results.

MongoDB experienced a 48-hour partial outage in Azure West Europe where customers encountered nodes reporting as "down" and delayed cluster modifications. The incident affected MongoDB Cloud services in the region, with MongoDB handling primary failover across the three available availability zones. The issue was resolved after instances began recovering, and all Atlas clusters in the region returned to healthy and fully operational status.

A billing bug in MongoDB Atlas caused some customers to receive higher-than-expected backup charges on their April 24, 2026 invoices. The issue was purely billing-related and did not affect backup configurations, cluster health, or customer data. MongoDB resolved the bug within 3.6 hours and automatically refunded all overcharges, with correct usage amounts reflected by April 28th.

MongoDB Atlas for Government experienced a major outage where the Business Intelligence Connector failed completely, preventing users from connecting to and querying their BI Connectors for nearly 93 hours. The issue was identified on April 17th and resolved on April 21st after implementing a fix. While BI Connector functionality was unavailable, underlying cluster health remained unaffected and data stayed accessible through regular MongoDB clients.

MongoDB Cloud experienced delays in cluster creation and adding new nodes specifically in the Azure East US 2 region due to Azure capacity constraints. Users encountered provisioning delays for new clusters and expansion of existing clusters in this region. The issue was resolved after 1.4 hours when Azure capacity constraints were lifted, restoring normal provisioning capabilities.

MongoDB Atlas experienced intermittent HTTP 503 errors affecting the Atlas Admin API and automation tooling like Terraform for nearly 40 hours. The errors caused control plane operations to fail temporarily, though requests typically succeeded on retry and database connectivity remained unaffected. The engineering team identified the root cause, applied a fix, and confirmed resolution after monitoring showed no further error spikes.

MongoDB Atlas Data Federation experienced a major issue preventing it from reading data from customer Azure blob storage containers. The problem affected all Atlas Data Federation queries attempting to access Azure blob storage data sources. The issue was identified, fixed, and resolved after 1.2 hours of service disruption.