MongoDB Atlas outage: Increase in Billing for Backup Usage

Affected components

• MongoDB Cloud

1. resolvedApr 27, 2026, 20:50 UTC

   We have resolved the issue that caused the overage and usages should be reflected correctly by April 28th. If you still see incorrect usages after this date, please reach out to us.

2. identifiedApr 27, 2026, 17:16 UTC

   We have identified a bug affecting some Atlas customers that resulted in higher-than-expected backup charges on invoices for the billing date of April 24, 2026. This is a billing-only issue; your backup configuration, cluster health, and data are unaffected. We are actively working to correct all affected invoices. Any overcharges will be automatically refunded — no action is required on your end. Please contact MongoDB Support with any questions. We will post another update by April 27 at 22:00 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.

• 1Password: Login and Sync IssuesCritical · Apr 27, 2026, 14:54 UTC
• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• LaunchDarkly: Delayed Metrics ingest in EUMinor · Apr 27, 2026, 15:39 UTC
• Mux: Issues downloading MP4 assetsMinor · Apr 27, 2026, 20:08 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