Changes / MongoDB Atlas / GCP capacity constraints affecting Atlas deployments
MongoDB Atlas: Major incident: GCP capacity constraints affecting Atlas deployments
Summary
MongoDB Atlas reported a major incident affecting some customers’ deployments due to GCP capacity constraints across North America, Europe, and Asia Pacific/Australia, including M50 and S70L instance types. It started at 2026-08-05 05:17 UTC and was resolved at 2026-08-05 12:14 UTC, lasting 6 h 56 min; MongoDB said symptoms had largely subsided and Atlas was fully operational.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: GCP capacity constraints affecting Atlas deployments
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-08-05 05:17 UTC
Before: not present
After: 2026-08-05 12:14 UTC
Before: not present
After: MongoDB Cloud
Before: not present
After: We are investigating an issue with Google Cloud Platform (GCP) capacity that is affecting some MongoDB Atlas customers across multiple GCP regions and geographies. We expect the scope of this issue to continue to expand as our investigation progresses. It currently includes, but is not limited to, multiple GCP regions across North America, Europe, and Asia Pacific/Australia, as well as M50 and S70L instance types.
Customers may experience errors or delays when creating or modifying Atlas clusters, particularly deployments with search nodes. Some customers may also see host-down alerts while this issue is ongoing.
MongoDB is working with GCP to understand the scope of the issue and restore capacity.
Customers encountering provisioning issues may retry later or consider using a different GCP region, cloud provider, or instance size. If you are experiencing a time-sensitive production impact, please contact MongoDB Support through the Support Portal or the in-product support chat.
We will provide another update as more information becomes available.
Before: not present
After: We believe the symptoms of this have largely subsided, looking at both customer cases and our internal metrics. We will share any more information as we get it, but for now resolving this incident as Atlas is fully operational.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: GCP capacity constraints affecting Atlas deployments (this change) MongoDB Atlas reported a major incident affecting some customers’ deployments due to GCP capacity constraints across North America, Europe, and Asia Pacific/Australia, including M50 and S70L instance types. It started at 2026-08-05 05:17 UTC and was resolved at 2026-08-05 12:14 UTC, lasting 6 h 56 min; MongoDB said symptoms had largely subsided and Atlas was fully operational. | Major incident |
All MongoDB Atlas changes → · MongoDB Atlas profile · Markdown · JSON