outages.live
Live
MongoDB AtlasIncident · 2026-08-19 20:45 UTC

Issues rotating certificates for projects containing only Atlas Free and Flex clusters

ResolvedOfficial update

This incident has been resolved.

The latest update from MongoDB Atlas.

State

Resolved

Started

74 d ago

2026-08-19 20:45 UTC

Lasted

25 h 21 min

until 2026-08-20 22:07 UTC

Worst impact

Notice

Timeline

7 updates
20:4503:0609:2615:4622:07
NoticeUpdate postedTimes in UTC

Identified

1 h 5 min 4%

Monitoring

24 h 16 min 96%

Updates

Times in UTC

As posted by MongoDB Atlas

Resolved2026-08-20 22:07 UTC

This incident has been resolved.

Monitoring2026-08-20 21:39 UTC

We have deployed fix, continuing the monitor for any further issues.

Monitoring2026-08-19 22:00 UTC

We are continuing to monitor for any further issues.

Monitoring2026-08-19 21:58 UTC

We are continuing to monitor for any further issues.

Monitoring2026-08-19 21:57 UTC

We are continuing to monitor for any further issues.

Monitoring2026-08-19 21:50 UTC

We performed remediation steps on all impacted projects. We will continue to monitor for more occurrences of this issue.

Identified2026-08-19 20:45 UTC

We have identified an issue impacting certain projects containing only Free or Flex clusters. For those clusters, TLS certificates are not being rotated correctly. This could lead to an inability to connect to your Free or Flex cluster. We are working on remediation steps.

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

5.1× 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

MongoDB Atlas·GCP Availability Zone europe-west2-b connectivity issues

This incident has been resolved.

Resolvedresolved 12 d ago

MongoDB Atlas·Issue impacting Atlas Search availability on certain clusters

This incident has been resolved.

Resolvedresolved 23 d ago

MongoDB Atlas·Admin Admin API: Intermittent Increase in 5xx errors

This incident has been resolved.

Resolvedresolved 23 d ago

MongoDB Atlas·MongoDB Charts: Infinite login loop when creating new Charts projects

This incident has been resolved.

Resolvedresolved 30 d ago

MongoDB Atlas·Trigger processing may be delayed globally

This incident has been resolved.

Resolvedresolved 31 d ago

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