MONGODB

🟠 MongoDB's billing dashboard is taking an unplanned vacation while AWS figures out how to count. The services actually work fine—it's just the part where they tell you how much it costs that's broken. Spoiler: when they fix it, the bill's gonna be spicy. (Auto-resolved: no updates in 24h)

⏰ Jul 17, 2026 Fixed (for now) spotted via status_rss

// The official story

MongoDB Atlas and Atlas for Government: New AWS Backup and AWS Data Transfer costs will be unavailable between July 17 and 20

// Status page says

Jul 17 , 16:14 UTC Identified - Due to an ongoing incident with AWS's billing data, MongoDB Atlas and Atlas for Government will not be updating AWS network or backup consumption data over this weekend, 2026-07-17 through 2026-07-20. The products themselves will remain fully available. When the upstream issue has been resolved, we intend to display and bill for the correct amounts. Charges will have usage dates that correctly express

🔗 Official status page (for the PR-approved version)

https://status.mongodb.com/incidents/qjk952jxg2kk

Mongodb's Greatest Hits

🟢 MONGODB 4d ago

🟠 MongoDB's search engine decided to take a unilateral vacation, leaving some users' queries stranded at the terminal. Engineers are frantically implementing a fix while mongot processes contemplate their career choices. (Auto-resolved: no updates in 24h)

🟢 MONGODB Sep 16, 2026

🟡 MongoDB's support portal ghosted users mid-morning, leaving developers to fend for themselves. Engineers are investigating why the one place you go for help decided to stop helping. Irony tastes like cold coffee and regret. (Auto-resolved: no updates in 24h)

🟢 MONGODB Sep 11, 2026

🟠 Let's Encrypt went full unreliable ex, and now MongoDB can't issue certificates without them. Free and flex tier clusters are stuck in provisioning limbo while the encryption gods argue with each other. (Auto-resolved: no updates in 24h)

🟢 MONGODB Jul 23, 2026

🔴 Atlas clusters in Azure West US are playing hide-and-seek with their own nodes. Connectivity drops, node communication fails, cluster ops crawl. Azure's networking layer apparently forgot what it was supposed to do. Grab coffee, this is a waiting game. (Auto-resolved: no updates in 24h)