Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Future Consideration
Categories Atlas
Created by Kerstin Nieter
Created on Dec 9, 2025

Block Maintenance Window After Severity Incident Recovery

What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

After a cluster recovers from a severity incident/outage, the system may trigger maintenance operations (if you don't have set a maintenance window) shortly afterward, including updates or patching.


What would you like to see happen?

Describe the desired outcome or enhancement.

Add functionality to block maintenance windows automatically after a cluster comes back online following a severity event.
Only highly critical security patches should override this block. Minor upgrades should wait until customer-approved window.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

Customers experience instability or risk while recovering from incidents, making troubleshooting and monitoring more difficult. Non-critical updates occurring immediately post-incident increases operational overhead.

What steps, if any, are you taking today to manage this problem?

/


  • Admin
    Christopher Shum
    Feb 6, 2026

    Thanks for your feedback — we hear you loud and clear. If you have a maintenance window configured, Atlas lets you defer the planned maintenance by up to two weeks. We also recognize the need for a better way to provide feedback to Atlas when your applications may be degraded, and we will take this into account as we evaluate improvements.