Companies / MongoDB Atlas / incidents
MongoDB Atlas: Trigger processing may be delayed globally
MongoDB Atlas reported a major global incident affecting Triggers: unordered processing was delayed, and some triggers were not firing or visible in the Atlas UI. The incident started at 2026-10-01 15:41 UTC and was resolved at 2026-10-01 20:54 UTC, lasting 5 h 12 min; trigger processing was operational by 19:59 UTC.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: MongoDB Atlas App Services and Device Sync
Timeline of updates
- investigating
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.
- investigating
We are continuing to investigate this issue.
- investigating
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.
- monitoring
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.
- resolved
This incident has been resolved.
Rewindex changes for this incident
- Major incident: Trigger processing may be delayed globally 2026-10-01 15:41 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). MongoDB Atlas profile · Recent MongoDB Atlas incidents · Markdown · JSON