Major incident

MongoDB Cloud: Trigger processing may be delayed globally

Oct 1, 2026, 15:41 UTC
started
20:54 UTC
resolved
5 h 13 min
duration

Affected: MongoDB Atlas App Services and Device Sync

Current status of MongoDB Cloud: Operational — live MongoDB Cloud status

Timeline

  1. Oct 1, 2026, 15:41 UTC
    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.
  2. Oct 1, 2026, 18:21 UTC
    investigating
    We are continuing to investigate this issue.
  3. Oct 1, 2026, 19:51 UTC
    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.
  4. Oct 1, 2026, 19:59 UTC
    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.
  5. Oct 1, 2026, 20:54 UTC
    resolved
    This incident has been resolved.

Updates as published by MongoDB Cloud (original).

Other services with incidents at the same time

This was part of a wider event: 27 services reported incidents within the hour.

More MongoDB Cloud incidents