BREAKING: MongoDB Atlas AWS Backup & Data Transfer Costs Unavailable July 17-20 [qjk952jxg2kk]
MongoDB Atlas is experiencing service degradation: AWS Backup and AWS Data Transfer cost visibility will be unavailable July 17-20. Immediate workarounds for indie hackers inside.
INCIDENT ALERT: MongoDB Atlas Service Impact
Status: Identified | Severity: Medium | Duration: July 17-20, 2024
---
What's Down & Who's Affected
MongoDB Atlas is temporarily disabling cost visibility for:
AWS Backup costs – you won't see backup storage charges
AWS Data Transfer costs – outbound data transfer costs hidden from dashboardThis impacts both standard MongoDB Atlas and Atlas for Government deployments on AWS. Your databases remain operational, but cost tracking and billing transparency are affected.
Who this hits hardest: Indie hackers monitoring burn rate, startups on tight budgets, anyone doing cost analysis or forecasting during this window.
---
Immediate Workarounds (DO THIS NOW)
1. Export Your Current Billing Data
Log into Atlas → Organization Settings → Billing
Screenshot or export your current cost dashboard before July 17
Save your AWS bill PDF from your AWS account as backup reference2. Use AWS Console Directly
Go to AWS Cost Explorer in your AWS account
Filter by service: "MongoDB Atlas"
You'll see actual charges even if Atlas dashboard is dark
Set up cost anomaly detection in AWS (takes 2 minutes)3. Enable Atlas Billing Alerts NOW
Atlas → Organization Settings → Billing → Set alert threshold
Get emailed if costs exceed your limit (works independently of UI)4. Track Manually
Document your current baseline costs
Compare your AWS invoice on Aug 1 to pre-incident levels
MongoDB will backfill cost data post-incident---
How to Check if YOUR Project is Affected
✓ You're affected if:
You use MongoDB Atlas clusters on AWS
You have Government Atlas clusters on AWS
You actively monitor costs via the Atlas dashboard
You're on any cluster tier (free, shared, dedicated)✗ You're NOT affected if:
You only use Atlas for application data (database operations work fine)
You don't care about cost visibility for 3 days
You use Azure or GCP deployments (only AWS impacted)Check your deployment region: Atlas → Clusters → Your cluster → Cloud Provider (should say "AWS")
---
Alternative Tools to Consider (Interim)
AWS Cost Explorer – free, native AWS billing dashboard
CloudZero – cost monitoring (free tier available)
Kubecost – if you're on Kubernetes
Your own cost tracking spreadsheet – honestly valid for 3 days---
Monitor Recovery
Official Status Page:
Check: https://status.mongodb.com
Subscribe to updates (don't just refresh)
MongoDB commits to updates every 6 hours minimumWhat to expect:
July 20, EOD: Cost visibility returns
July 21-22: Backfilled historical cost data populated
No data loss, no functionality loss – purely UI/reportingPost-incident:
Verify costs match your AWS bill
Document any discrepancies for MongoDB support
Resume normal cost monitoring---
Bottom Line
Your databases work fine. You just can't see certain costs for 72 hours. Export data now, use AWS console as backup, set alerts, and monitor status page. This is inconvenient, not catastrophic.
Stay calm. Stay shipped.