MongoDB Atlas incident: Atlas UI and API Periodic Unavailability

Affected components

• MongoDB Cloud

1. resolvedAug 18, 2026, 15:17 UTC

   This incident has been resolved. Following the incident, we identified an issue that caused some internal Atlas jobs not to start as scheduled, resulting in delays to certain changes. The issue was related to this incident "Atlas UI and API Periodic Unavailability" which has been remediated. Customer clusters and their data were not affected; the impact was limited to the timing of control-plane operations. This jobs issue has been resolved as well.

2. monitoringAug 18, 2026, 15:04 UTC

   We have disabled the workload and are monitoring the situation

3. identifiedAug 18, 2026, 14:57 UTC

   We have identified a new workload that was putting more load than expected on the backing system. We are working on disabling it. Customer clusters remain unaffected.

4. investigatingAug 18, 2026, 14:10 UTC

   We are investigating an issue where customers periodically cannot access the Atlas UI or utilize the API. Customer clusters are unaffected.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in MongoDB Atlas's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• Snowflake: INC20000163Major · Aug 18, 2026, 12:58 UTC
• OVHcloud: [GRA5/7/9/11][Compute - Instance] - Some instances incident notificationMajor · Aug 18, 2026, 14:34 UTC
• Akamai: Connection drops and increased latency in MiamiMinor · Aug 13, 2026, 19:31 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC

How often does MongoDB Atlas have incidents?

MongoDB Atlas reported 15 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 31m. See MongoDB Atlas's uptime and incident history