MongoDB Atlas reported this major-impact incident on its official status page on Oct 1, 2026, 15:41 UTC. It was resolved after 5h 13m.
Right now MongoDB Atlas is operational. Live MongoDB Atlas status →
This incident has been resolved.
Atlas Triggers are firing again, and trigger processing is operational. We are monitoring the service and verifying the status of triggers affected during the incident, including any delayed events. We will provide a further update once verification is complete.
Some users may find that their Atlas Triggers are not firing or are not visible in the Atlas UI. We are investigating both symptoms and working to restore trigger processing. We will provide another update as we learn more.
We are continuing to investigate this issue.
As of approximately 15:00 UTC, some users of MongoDB Atlas Triggers may experience delayed unordered trigger processing. We are investigating and working to restore normal processing.
Overlapping incidents aren't necessarily related.
MongoDB Atlas reported 15 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 31m. See MongoDB Atlas's uptime and incident history