MongoDB Atlas incident: Atlas Backup Export Jobs Degraded Performance

Affected components

• MongoDB Atlas for Government
• MongoDB Cloud

1. resolvedMay 7, 2026, 20:55 UTC

   This incident has been resolved.

2. monitoringMay 7, 2026, 20:02 UTC

   A fix has been implemented and we are monitoring the results.

3. identifiedMay 7, 2026, 01:20 UTC

   We are continuing to work on the fix for this issue. We will have another update by May 7 16:00 UTC.

4. identifiedMay 6, 2026, 21:48 UTC

   Identified - We have identified an issue causing failures for a subset of Atlas backup export jobs. We are actively working on a fix. Your cluster health and data are unaffected. We will provide another update by May 7 01:30 UTC

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.

• LiveKit: Outbound SRTP calls are failingMajor · May 6, 2026, 19:46 UTC
• Render: HA Postgres UnavailabilityMajor · May 7, 2026, 02:00 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• Mailgun: Automatic Sender Security Records Not ProvisioningMinor · May 6, 2026, 15:40 UTC
• Snyk: Issues API DelaysMinor · May 6, 2026, 20:45 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