Changes / MongoDB Atlas / Increase in Billing for Backup Usage
MongoDB Atlas: Major incident: Increase in Billing for Backup Usage
Summary
MongoDB Atlas reported a major billing-only bug causing higher-than-expected backup charges on April 24, 2026 invoices; backups, cluster health and data were unaffected. The incident ran from 2026-04-27 17:16 UTC to 2026-04-27 20:50 UTC (3 h 33 min). MongoDB resolved the issue, promised automatic refunds, and said usage should display correctly by April 28th.
Machine-written from the diff below (Sol; type: incident other). Check the diff before relying on it.
What changed
Before: not present
After: Increase in Billing for Backup Usage
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-04-27 17:16 UTC
Before: not present
After: 2026-04-27 20:50 UTC
Before: not present
After: MongoDB Cloud
Before: not present
After: 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.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Increase in Billing for Backup Usage (this change) MongoDB Atlas reported a major billing-only bug causing higher-than-expected backup charges on April 24, 2026 invoices; backups, cluster health and data were unaffected. The incident ran from 2026-04-27 17:16 UTC to 2026-04-27 20:50 UTC (3 h 33 min). MongoDB resolved the issue, promised automatic refunds, and said usage should display correctly by April 28th. | Major incident |
All MongoDB Atlas changes → · MongoDB Atlas profile · Markdown · JSON