Atlas is experiencing issues with issuing certificates from Lets Encrypt
This incident has been resolved.
The latest update from MongoDB Atlas.
State
Resolved
Started
51 d ago
2026-09-11 01:28 UTC
Lasted
2 h 23 min
until 2026-09-11 03:51 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
33 min 23%
Monitoring
1 h 50 min 77%
Updates
Times in UTCAs posted by MongoDB Atlas
This incident has been resolved.
Atlas is seeing elevated errors rates of certificate issuance due to a Let's Encrypt outage (https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/6aa35c1d892d7304f2747e01). Free and flex tier cluster provisioning may be delayed.
We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Free and Flex cluster provisioning may be delayed.
Affected components
2MongoDB Atlas in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
90
Median duration
5 h
This incident
52% shorter than the median
Other MongoDB Atlas incidents
All incidentsMongoDB Atlas·GCP Availability Zone europe-west2-b connectivity issues
This incident has been resolved.
MongoDB Atlas·Issue impacting Atlas Search availability on certain clusters
This incident has been resolved.
MongoDB Atlas·Admin Admin API: Intermittent Increase in 5xx errors
This incident has been resolved.
MongoDB Atlas·MongoDB Charts: Infinite login loop when creating new Charts projects
This incident has been resolved.
MongoDB Atlas·Trigger processing may be delayed globally
This incident has been resolved.
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.
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.
https://outages.cc/feed.xml?providers=mongodb/feed subscribe https://outages.cc/feed.xml?providers=mongodbFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane