MongoDB Atlas Status · History · Incident #6017
RESOLVEDDelayed cluster configuration affecting free and flex users
Minor · Started Jul 29, 2026 · 6:55 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
MongoDB Atlas Status · History · Incident #6017
RESOLVEDMinor · Started Jul 29, 2026 · 6:55 PM
Duration
41m
Severity
Minor
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
Jul 29, 2026 · 6:55 PM
Resolved
Jul 29, 2026 · 7:37 PM
Duration
41m
Severity
Minor
Event timeline
Investigating
Jul 29 · 6:55 PM MongoDB AtlasWe are investigating an issue with cluster configuration updates getting delayed for a subset of users on free and flex tiers. Cluster access is unaffected.
Identified
Jul 29 · 7:06 PM MongoDB AtlasWe have identified the root cause and are rolling out a configuration change to remediate the delayed cluster configuration changes.
Monitoring
Jul 29 · 7:31 PM MongoDB AtlasWe have seen errors subsiding and cluster configurations for free and flex customers should be operating normally again.
Resolved
Jul 29 · 7:37 PM MongoDB AtlasThis incident has been resolved.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.