Live

GCP capacity constraints affecting Atlas deployments

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.

The latest update from MongoDB Atlas.

State

Resolved

Started

88 d ago

2026-08-05 05:17 UTC

Lasted

6 h 57 min

until 2026-08-05 12:14 UTC

Worst impact

Partial outage

Timeline

2 updates
05:1707:0108:4510:2912:14
Partial outageUpdate postedTimes in UTC

Investigating

6 h 57 min 100%

Updates

Times in UTC

As posted by MongoDB Atlas

Resolved2026-08-05 12:14 UTC

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.

Investigating2026-08-05 05:17 UTC

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

Affected components

1
MongoDB Cloud

MongoDB Atlas in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

14

Days with an incident

90

Median duration

5 h

This incident

1.4× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

59 days
median 5 h
90 days agoToday

Other MongoDB Atlas incidents

All incidents

Follow MongoDB Atlas

Your coding agent knows when MongoDB Atlas is down, and tells you when a failure is theirs, not yours. You can also get MongoDB Atlas incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "mongodb" and tell me if MongoDB Atlas has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=mongodb
Slack
/feed subscribe https://outages.cc/feed.xml?providers=mongodb

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane