MongoDB incident

Increase in Billing for Backup Usage

Major Resolved View vendor source →

MongoDB experienced a major incident on April 27, 2026 affecting MongoDB Cloud, lasting 3h 33m. The incident has been resolved; the full update timeline is below.

Started
Apr 27, 2026, 05:16 PM UTC
Resolved
Apr 27, 2026, 08:50 PM UTC
Duration
3h 33m
Detected by Pingoru
Apr 27, 2026, 05:16 PM UTC

Affected components

MongoDB Cloud

Update timeline

  1. identified Apr 27, 2026, 05:16 PM 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 24 at 22:00 UTC.

  2. resolved Apr 27, 2026, 08:50 PM 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.